Mew tootcat-mw https://mew.toot.cat/mw/Main_Page MediaWiki 1.35.0 first-letter Media Special Talk User User talk Mew Mew talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk 10 176 568 2006-01-30T19:38:10Z Woozle 1 wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 569 568 2006-04-09T19:29:18Z Woozle 1 Template:Faint moved to Template:faint wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 570 569 2008-06-19T03:37:16Z htyp>NoracLetoc 0 cnatabo wikitext text/x-wiki [http://www.householdcavalry.co.uk/ubb/Forum4/private/1599.html sex clip] [http://livetutoring.net/albums2/gallery/news653.html wwf the kat] [http://martialartsinstitute.net/modules/xoopsgallery/js/txt/new2363.htm my cousin vinny movie posters] [http://solicitorsireland.com/images/pics/comment33.htm movie upcoming] [http://mbproducts.com/contact-log/september/index.htm index] [http://www.dansk.ie/ssp_director/albums/album-2/1863.htm available error not site web] [http://aisa.org.af/test/typo3temp/cs/style/text-389.html samba dance video clip] [http://canazone.com/upload/images/text-1672.htm oxford dictionary crack] [http://itrendsinc.com/splash/pixbak/icons/topic1237.htm child music] [http://solicitorsireland.com/images/pics/comment1219.htm moviesarenas] [http://www.scrapheap-challenge.com/badkarma/store/files/news51.html advanced x video converter serial 3.9.18] [http://www.dar.ie/uploads/images/pixel/resource620.htm raven riley movie] [http://thewitchesway.co.uk/shop/catalog/images/html/comment-2555.htm alvin chipmunk video watch] [http://yamcanada.com/asahi_files/2006/20.htm nonnude preteen models] [http://magickalmoon.com/creative/thumbs/rss/news-574-2008-05-31.html eden isle katrina] [http://lastwizards.com/news/data/backup/march28/news-2769-2008-05-30.html inmate family services] [http://hbo.com.pk/emails/images/avatars/picture/cazeld.html electric guitar action setup] [http://jhigoodidea.com/blog/wp-content/themes/JHI/css/ie/cacelno1493.htm dry cleaners] [http://juliakimsmith.com/files/gimgs/pics/topic90.htm restasis and side effects] [http://hazirci.us/uploads/fotos/thumbs/topic106.htm noam chomsky biography] [http://garyhall.org/gallery/albums/album02/nocorol1227.htm make ringtones nokia 6255i] [http://hbo.com.pk/emails/images/avatars/picture/trmexe.html sixteen candles movie cast] [http://www.dansk.ie/ssp_director/albums/album-2/904.htm la minita] [http://magickalmoon.com/creative/thumbs/rss/news-1449-2008-06-04.html exercise pilates video winsor] [http://st-andrewschurch.co.uk/images/uploads/icons/news-410.html type of lentil] [http://connectethiopia.com/committee/images/thumbs/779.html aerobic capacity test] [http://dostshell.com/cafe/uploads_user/2000/article565.htm carmina burana] [http://tipperaryauctioneers.com/admin/admin_blog/content/09/article855.htm audio video production orlando] [http://age-me.com/forums/store/inst/resource-1762.html nepotism] [http://soundshorechorale.com/galeri/thumbnail/pics/comment1717.htm ogden alc] [http://arianepoole.com/shopimages/products/normal/pics/text-1082.html general merchandise wholesale] [http://tipperaryauctioneers.com/admin/admin_blog/content/09/article1955.htm gangbang cum] [http://rsturk.com/files/xml/article2383.html nine inch nail the perfect drug lyric] [http://www.householdcavalry.co.uk/ubb/Forum4/private/2654.html lemon meringue pie recipe] [http://blog.mud-ti.com/wp-content/uploads/2008/02/916.htm dynojet] [http://afghantelecom.af/include/scripts/topic22.htm marylin manson sweet dreams video] [http://connectethiopia.com/committee/images/thumbs/1865.html movie heavens gate] [http://connectethiopia.com/committee/images/thumbs/2395.html interfacce] [http://msnrazzi.net/wp-content/uploads/2008/04/sitemap.htm www] [http://mbproducts.com/contact-log/september/bastro1455.htm combi strollers] [http://www.mtnstreams.com/ssp_director_7/config/conf/ercafo.html moloney murine sarcoma virus] [http://hbo.com.pk/emails/images/avatars/picture/zelacx.html julie clarke pics] [http://jhigoodidea.com/blog/wp-content/themes/JHI/css/ie/index.htm sitemap] [http://www.householdcavalry.co.uk/ubb/Forum4/private/2062.html odeon richmond] [http://st-andrewschurch.co.uk/images/uploads/icons/news-1419.html entertainment look video] [http://jhigoodidea.com/blog/wp-content/themes/JHI/css/ie/ettacadar2466.htm skagit county sheriffs department] [http://jhigoodidea.com/blog/wp-content/themes/JHI/css/ie/vardesa2510.htm old girls] [http://christchurchchildren.org/weblog/images/uploads/thumbs/index.htm site] [http://tipperaryauctioneers.com/admin/admin_blog/content/09/article1267.htm just friends movie trailer] [http://www.scrapheap-challenge.com/badkarma/store/files/news2041.html a change would do you good video] [http://sanalviva.com/forum/attachments/images/news1336.html acts assisted living] [http://snt.org.pk/chat/chat/localization/czech/thumb/topic-1317.html performance bond definition] [http://rsturk.com/files/xml/article1778.html king county superior court rules] [http://juliakimsmith.com/files/gimgs/pics/topic301.htm hogans heroes] [http://hazirci.us/uploads/fotos/thumbs/topic389.htm huge bra busters] [http://blog.mud-ti.com/wp-content/uploads/2008/02/1681.htm colorado trial lawyers] [http://www.dar.ie/uploads/images/pixel/resource284.htm cad programs] [http://jhigoodidea.com/blog/wp-content/themes/JHI/css/ie/heneltt124.htm ethereal download for window] [http://thewitchesway.co.uk/shop/catalog/images/html/comment-509.htm movie masters warwick] [http://www.scrapheap-challenge.com/badkarma/store/files/news1218.html for good wicked] [http://sanalviva.com/forum/attachments/images/news1008.html cum overdose] [http://yamcanada.com/asahi_files/2006/1083.htm at london business school] [http://yamcanada.com/asahi_files/2006/407.htm free dragon ball z hentai] [http://afghanexperts.gov.af/gallery/albums/userpics/10002/news-187-20080512.html utah financial institutions] [http://www.householdcavalry.co.uk/ubb/Forum4/private/1383.html number one spot video] [http://dostshell.com/cafe/uploads_user/2000/article2011.htm rainbow six lockdown videos] [http://martialartsinstitute.net/modules/xoopsgallery/js/txt/new1826.htm www.camcrush.com] [http://lastwizards.com/news/data/backup/march28/news-745-2008-05-27.html shark and surfer video] [http://thewitchesway.co.uk/shop/catalog/images/html/sitemap.htm sitemap] [http://snt.org.pk/chat/chat/localization/czech/thumb/topic-567.html mashas world] [http://mbproducts.com/contact-log/september/zarcaal560.htm pc torrent sites] [http://christchurchchildren.org/weblog/images/uploads/thumbs/text514.htm persuasion topics] [http://hoysted.com/gallery/albums/album02/article-1794.htm sierra vista homes for sale] [http://st-andrewschurch.co.uk/images/uploads/icons/news-1343.html alamo car] [http://www.scrapheap-challenge.com/badkarma/store/files/news703.html male beefcake] [http://sanalviva.com/forum/attachments/images/news739.html dogs mating] [http://solicitorsireland.com/images/pics/comment1787.htm kristin laura kreuk] [http://soulfoodcookbook.com/ubb/Forum6/forum/index.htm home] [http://snt.org.pk/chat/chat/localization/czech/thumb/topic-2803.html ihigh.com] [http://nationalassembly.af/downloads/images/relolet.html behind these hazel eyes lyrics] [http://www.orixaviation.com/htm/de/css/styles/topic-655.htm adipex great buy] [http://dostshell.com/cafe/uploads_user/2000/article1426.htm leftover crack one dead cop guitar tab] [http://recycledsoftware.com/xcart/images/E/pasenzdar-1288.html arp 2600 v crack] [http://royaldublinfusiliers.com/forum_backup/docs/readme/comment604.htm free court records] [http://arianepoole.com/shopimages/products/normal/pics/text-1610.html in twain] [http://www.dansk.ie/ssp_director/albums/album-2/sitemap.htm home] [http://magickalmoon.com/creative/thumbs/rss/news-376-2008-06-03.html cuesta college] [http://sanalviva.com/forum/attachments/images/news345.html epidural steroid injection] [http://www.householdcavalry.co.uk/ubb/Forum4/private/1508.html record producer midi edition serial] [http://audiovideomix.com/albums2/truley/text443.htm arial audio converter 2.1.4 serial] [http://a2kat.com/rar/backup/dump/fuvarfo.html smoking drugs alcohol] [http://seal.org.af/uploads/images/thumbs/resource-2063.html mr sparkle car wash] [http://rsturk.com/files/xml/article633.html adult chat free room video yahoo] [http://connectethiopia.com/committee/images/thumbs/805.html pure digital technologies video camera] [http://christchurchchildren.org/weblog/images/uploads/thumbs/text511.htm newport bedding company] [http://seal.org.af/uploads/images/thumbs/resource-2019.html fastin adipex overnight 89] [http://recycledsoftware.com/xcart/images/E/varzarenb-2181.html table runners] [http://christchurchchildren.org/weblog/images/uploads/thumbs/text978.htm vintage cunts] [http://snt.org.pk/chat/chat/localization/czech/thumb/topic-354.html san diego weather] [http://www.mentalhealthireland.ie/pressreleases/docs/1649.html anchorage alaska realtor] [http://itrendsinc.com/splash/pixbak/icons/topic787.htm south jersey wedding rentals] [http://st-andrewschurch.co.uk/images/uploads/icons/news-1555.html licensed day care facilities] [http://aisa.org.af/test/typo3temp/cs/style/text-1242.html need for speed high stakes no cd crack] [http://www.orixaviation.com/htm/de/css/styles/topic-518.htm laurie anderson] [http://ictconference.org.af/gallery/albums/userpics/10002/article-881.htm audiocatalyst crack 2.1] [http://solicitorsireland.com/images/pics/comment401.htm unigraphics class] [http://dostshell.com/cafe/uploads_user/2000/article1681.htm bare essentials mineral make up] [http://hbo.com.pk/emails/images/avatars/picture/cnaenlob.html tysons creek baptist church] [http://seal.org.af/uploads/images/thumbs/resource-2255.html adipex or phentermine 37.5 mg] [http://www.dar.ie/uploads/images/pixel/resource1420.htm mushroom supplies] [http://hoysted.com/gallery/albums/album02/article-379.htm alvin cartoon chipmunk home video] [http://homefindersplus.com/documents/docs/article1426.html african art drugs] [http://magickalmoon.com/creative/thumbs/rss/news-859-2008-05-30.html oh yeah little april] [http://livetutoring.net/albums2/gallery/news320.html al moazen activation code] [http://yamcanada.com/asahi_files/2006/503.htm supra drag videos] [http://solicitorsireland.com/images/pics/comment638.htm stupid gross videos] [http://yamcanada.com/asahi_files/2006/544.htm asian clip free hardcore movie] [http://www.mentalhealthireland.ie/pressreleases/docs/1716.html el rocio accomodation] [http://rsturk.com/files/xml/article45.html strip show videos] [http://cprofit.com/res/userimages/icons/comment2052.htm tia] [http://brokerexec.com/gs/IDXIntegration/table/news-1334-2008-06-06.html new kids on the block video clips] [http://audiovideomix.com/albums2/truley/text1860.htm mexican pharmacy list] [http://hazirci.us/uploads/fotos/thumbs/topic1839.htm limousine service transportation] [http://royaldublinfusiliers.com/forum_backup/docs/readme/comment913.htm asian bukake] [http://rsturk.com/files/xml/index.html domain] [http://christchurchchildren.org/weblog/images/uploads/thumbs/text459.htm harley davidson accessories] [http://juliakimsmith.com/files/gimgs/pics/topic2471.htm eamon fuck it music video] [http://gameaddress.com/mysqldumper/work/backup/dump/comment-1648.html 12 volt rope lighting] [http://www.dar.ie/uploads/images/pixel/resource1369.htm reply music crack] [http://www.scrapheap-challenge.com/badkarma/store/files/news1017.html jetsons movie mp3] [http://dostshell.com/cafe/uploads_user/2000/article2163.htm sonic foundry video editor] [http://danasworld.biz/images/thumbs/text-180.html incredimail xe crack] [http://age-me.com/forums/store/inst/resource-1156.html lock folder xp v3 6 crack] [http://age-me.com/forums/store/inst/resource-736.html movie star height chart] [http://rsturk.com/files/xml/article1331.html lois family guy] [http://snt.org.pk/chat/chat/localization/czech/thumb/topic-1820.html marcil video] [http://juliakimsmith.com/files/gimgs/pics/topic1409.htm florida rentals] [http://garyhall.org/gallery/albums/album02/rolelt862.htm elegant expressions in sioux falls sd] [http://explore.ie/explore_lists/explore/conf/new119.htm apple preview movie] [http://enzyme-weight-loss.com/livehelp/txt-database/base/resource-772.html linkedin] [http://soulfoodcookbook.com/ubb/Forum6/forum/koeltzeld.htm permitted development right] [http://afghanexperts.gov.af/gallery/albums/userpics/10002/index.html www] [http://age-me.com/forums/store/inst/resource-2317.html exhibicionista info personal remember video] [http://garyhall.org/gallery/albums/album02/pldefo357.htm explorers movie 1985] [http://martialartsinstitute.net/modules/xoopsgallery/js/txt/new2820.htm park central] [http://age-me.com/forums/store/inst/resource-790.html explode head magnet monster video] [http://www.dansk.ie/ssp_director/albums/album-2/2082.htm chicago limo services] [http://homefindersplus.com/documents/docs/article115.html add drug link suggest] [http://rsturk.com/files/xml/article118.html antranikian] [http://www.orixaviation.com/htm/de/css/styles/topic-625.htm rome total war video clip] [http://rsturk.com/files/xml/article567.html morbid art] [http://www.householdcavalry.co.uk/ubb/Forum4/private/1777.html amoxicillin expired] [http://royaldublinfusiliers.com/forum_backup/docs/readme/comment543.htm tuscany subdivision] [http://thewitchesway.co.uk/shop/catalog/images/html/comment-799.htm adderall lsat] [http://royaldublinfusiliers.com/forum_backup/docs/readme/comment474.htm accidental hero movie] [http://magickalmoon.com/creative/thumbs/rss/news-820-2008-06-03.html real estate in worcester ma] [http://thewitchesway.co.uk/shop/catalog/images/html/comment-2529.htm lives of girls and women summary] [http://audiovideomix.com/albums2/truley/text1392.htm sony mdr ex71slb earphones] [http://enzyme-weight-loss.com/livehelp/txt-database/base/resource-1474.html ringtones for samsung] [http://age-me.com/forums/store/inst/resource-1834.html lady in waiting middle ages] [http://age-me.com/forums/store/inst/resource-2130.html sunami] [http://age-me.com/forums/store/inst/resource-2426.html bgafd] [http://rsturk.com/files/xml/article1079.html lion seul video] [http://tipperaryauctioneers.com/admin/admin_blog/content/09/article1957.htm gold buyers] [http://enzyme-weight-loss.com/livehelp/txt-database/base/resource-1026.html actress hot indian movie sizzling south] [http://danasworld.biz/images/thumbs/text-786.html money videos] [http://age-me.com/forums/store/inst/resource-2359.html ayashi no ceres video] [http://danasworld.biz/images/thumbs/text-1482.html nevada corporations] [http://homefindersplus.com/documents/docs/article1020.html lg vx6100 crack unlock code] [http://recycledsoftware.com/xcart/images/E/insitacel-1871.html leanna heart] [http://audiovideomix.com/albums2/truley/text1007.htm professional sony video camera] [http://thewitchesway.co.uk/shop/catalog/images/html/comment-2510.htm promotional products china] [http://www.orixaviation.com/htm/de/css/styles/topic-525.htm justice just for girls clothing store] [http://dostshell.com/cafe/uploads_user/2000/article138.htm lindsay lohan rumors music videos] [http://age-me.com/forums/store/inst/resource-2261.html ativan book com drug guest lyle site] [http://royaldublinfusiliers.com/forum_backup/docs/readme/index.htm domain] [http://jhigoodidea.com/blog/wp-content/themes/JHI/css/ie/eltfam1993.htm adobe premiere pro serials] [http://yamcanada.com/asahi_files/2006/734.htm pepe le pew videos] [http://audiovideomix.com/albums2/truley/text1182.htm white siberian tiger] [http://snt.org.pk/chat/chat/localization/czech/thumb/topic-675.html java video chat room] [http://homefindersplus.com/documents/docs/article789.html score land videos] [http://a2kat.com/rar/backup/dump/henricq.html to_date sql examples] [http://cprofit.com/res/userimages/icons/comment1286.htm azures bittorent client] [http://www.orixaviation.com/htm/de/css/styles/topic-1046.htm free hairy pussy movies] [http://christchurchchildren.org/weblog/images/uploads/thumbs/text1193.htm loans for apartment complexes] [http://homefindersplus.com/documents/docs/article347.html naked man basketball video] [http://royaldublinfusiliers.com/forum_backup/docs/readme/comment1480.htm the circle game by joni mitchell] [http://hazirci.us/uploads/fotos/thumbs/topic2113.htm audio clips from movies] [http://ravzam.com/Forum/attachments/cache/comment-2425.htm ls videos] [http://1c-kursy.com/link/classes/css/page367.html space marines] [http://hoysted.com/gallery/albums/album02/article-1094.htm wilshire blvd los angeles] [http://magickalmoon.com/creative/thumbs/rss/news-1592-2008-06-03.html discounted gasoline] [http://hazirci.us/uploads/fotos/thumbs/topic398.htm kasia] [http://solicitorsireland.com/images/pics/comment1328.htm insaniquarium activation code] [http://dostshell.com/cafe/uploads_user/2000/article2076.htm xenical.us] [http://gameaddress.com/mysqldumper/work/backup/dump/comment-1138.html photosynthesis respiration cycle] [http://afghantelecom.af/include/scripts/sitemap.html web] [http://magickalmoon.com/creative/thumbs/rss/news-1107-2008-05-29.html night safari singapore zoo] [http://age-me.com/forums/store/inst/resource-225.html mike williams football video] [http://seal.org.af/uploads/images/thumbs/resource-780.html lady in the blue dress lyrics senses fail] <span style="color: #7f7f7f;">{{{1}}}</span> 554c51b2a1a0059c2cd73b0e1168ae6272de4088 571 570 2008-06-19T11:00:22Z Woozle 1 Reverted edits by [[Special:Contributions/NoracLetoc|NoracLetoc]] ([[User_talk:NoracLetoc|Talk]]); changed back to last version by [[User:Woozle|Woozle]] wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 572 571 2009-01-17T01:25:51Z htyp>NoracLetoc 0 http://cpaspfoks.hostinginfive.com/avi-to-mpeg-4-ipod-2009-01-06.htm wikitext text/x-wiki [http://cpaspfoks.hostinginfive.com/avi-to-mpeg-4-ipod-2009-01-06.htm avi to mpeg 4 ipod video file] [http://mexdomzar.hostinginfive.com/lafavim.html gmc vehicle recall] [http://nefuwalt.oamm.info/new1166.htm sharukh khan movies] [http://henlipn.hostinginfive.com/olomexxne.html russia sex video] [http://debrrolro.hostinginfive.com/comment750.htm birdy] <span style="color: #7f7f7f;">{{{1}}}</span> d57203820d4fe0420a91e63e0a5bd3979a216ccc 573 572 2009-01-17T02:05:31Z Woozle 1 Reverted edits by [[Special:Contributions/NoracLetoc|NoracLetoc]] ([[User_talk:NoracLetoc|Talk]]); changed back to last version by [[User:Woozle|Woozle]] wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 574 573 2009-01-17T02:05:54Z Woozle 1 Protected "[[Template:faint]]": popular template -- spam target [edit=sysop:move=sysop] wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 6 181 616 2017-12-31T10:07:56Z Woozle 1 [[category:screenshots]] * '''what''': screenshot of Dotster domain transfer tab while trying to (again) enter auth code for toot.cat wikitext text/x-wiki [[category:screenshots]] * '''what''': screenshot of Dotster domain transfer tab while trying to (again) enter auth code for toot.cat 865b411657b7f79c62b1ccdf014375fcccfa8826 0 175 556 2018-01-14T13:22:04Z Woozle 1 Created page with "==2018-01-14== My current plan is: # create a new Postgres db for toot.cat's Mastodon # migrate the data there # create new user "tootcat" # install Mastodon under "tootcat" #..." wikitext text/x-wiki ==2018-01-14== My current plan is: # create a new Postgres db for toot.cat's Mastodon # migrate the data there # create new user "tootcat" # install Mastodon under "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance 253a7d18afea5ab9bdf2ea07146c8b628cc8b165 557 556 2018-01-14T14:32:50Z Woozle 1 saving work wikitext text/x-wiki ==2018-01-14== My current plan is: # create a new Postgres db for toot.cat's Mastodon # migrate the data there # create new user "tootcat" # install Mastodon under "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ===Notes=== Inside /root/backups: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> Upgrading Mastodon: [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official] I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1) (possibly with '-' replaced by '_'). Probably just need to do this next: <code>CREATE DATABASE tootcat-masto-r1;</code> d7e14c5147bd083f20339b311da408e37befc65e 558 557 2018-01-14T17:18:28Z Woozle 1 wikitext text/x-wiki ==2018-01-14== My current plan is: # create a new Postgres db for toot.cat's Mastodon # migrate the data there # create new user "tootcat" # install Mastodon under "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ===Notes=== Inside /root/backups: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> Upgrading Mastodon: [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official] I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1) (possibly with '-' replaced by '_'). Probably just need to do this next: <code>CREATE DATABASE tootcat-masto-r1;</code> ...or, rather: <code>createdb --owner=tootcat tootcat-masto-r1</code> -- except do I need to create "tootcat" as a system user first? Or a db user? 2ccf9b50d45df837fb136d28d19e8e7fb951a9fb 559 558 2018-01-14T17:54:19Z Woozle 1 rearranged order slightly wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. ===Notes=== Inside /root/backups: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> Upgrading Mastodon: [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official] I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1) (possibly with '-' replaced by '_'). Probably just need to do this next: <code>CREATE DATABASE tootcat-masto-r1;</code> ...or, rather: <code>createdb --owner=tootcat tootcat-masto-r1</code> -- except do I need to create "tootcat" as a system user first? Or a db user? 1cad9880468431dd39096b418d376bc68d59fdb9 560 559 2018-01-14T19:37:15Z Woozle 1 saving work wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. ===Notes=== Inside /root/backups: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> Upgrading Mastodon: [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official] I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1) (possibly with '-' replaced by '_'). Probably just need to do this next: <code>CREATE DATABASE tootcat-masto-r1;</code> ...or, rather: <code>createdb --owner=tootcat tootcat-masto-r1</code> -- except do I need to create "tootcat" as a system user first? Or a db user? ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3==== [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. 5eef64308306135c42208fb6e3d014db2e55cf1b 561 560 2018-01-14T20:01:21Z Woozle 1 next thing to do wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here. 0c28b0415556c68c5172f80bd932bbfc5e460802 562 561 2018-01-14T20:03:28Z Woozle 1 /* step 4: installing Mastodon */ wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. d8937b4ba3a208f50de6d564ce554b1467fb9c8b 563 562 2018-01-14T20:30:47Z Woozle 1 /* step 4: installing Mastodon */ wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} 52da4e01cf5a431bdffb5cd553c9b613e90c9e2c 564 563 2018-01-14T23:19:11Z Woozle 1 /* step 4: installing Mastodon */ saving work wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} Skipping the bit about installing Ruby, since that is already installed on this server. chdir to <code>/home/tootcat/web</code>, then: : {{markup/tty|tootcat@tootcat:~/web$| git clone https://github.com/tootsuite/mastodon.git mastodon}} :: {{markup/tty|Cloning into 'mastodon'...}} :: {{markup/tty|remote: Counting objects: 56389, done.}} :: {{markup/tty|remote: Compressing objects: 100% (13/13), done.}} :: {{markup/tty|remote: Total 56389 (delta 0), reused 3 (delta 0), pack-reused 56376}} :: {{markup/tty|Receiving objects: 100% (56389/56389), 52.51 MiB | 30.41 MiB/s, done.}} :: {{markup/tty|Resolving deltas: 100% (37140/37140), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon/}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)}} :: {{markup/tty|Note: checking out 'v2.1.3'.}} :: <pre>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 35b8498... Skip ActivityPub Announces of non-public objects (#6230)</pre> : {{markup/tty|tootcat@tootcat:~/web/mastodon$| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|ERROR: While executing gem ... (Gem::FilePermissionError)}} :: {{markup/tty| You don't have write permissions for the /var/lib/gems/2.3.0 directory.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle exec rails c}} :: {{markup/tty/color|red|Could not find rake-12.3.0 in any of the sources}} :: {{markup/tty/color|orange|Run `bundle install` to install missing gems.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install}} :: {{markup/tty/color|orange|Warning: the running version of Bundler (1.15.3) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.}} :: {{markup/tty|Fetching gem metadata from https://rubygems.org/...........}} :: {{markup/tty|Fetching version metadata from https://rubygems.org/...}} :: {{markup/tty|Fetching dependency metadata from https://rubygems.org/..}} :: {{markup/tty|Fetching rake 12.3.0}} <pre> Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run: bundle install --path vendor/bundle to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo. Password: </pre> Decided this was not the way to do it, and logged in as root: : {{markup/tty|root@tootcat:~#| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|Successfully installed bundler-1.16.1}} :: {{markup/tty|Parsing documentation for bundler-1.16.1}} :: {{markup/tty|Installing ri documentation for bundler-1.16.1}} :: {{markup/tty|Done installing documentation for bundler after 9 seconds}} :: {{markup/tty|1 gem installed}} : {{markup/tty|root@tootcat:~#| bundle install --deployment --without development test}} :: {{markup/tty/color|orange|Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.}} :: {{markup/tty/color|red|Could not locate Gemfile}} Okay, so I guess it's back to the mastodon user... : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install --deployment --without development test}} :: This seemed to work: [[/paste/2018/01/14/01]] : {{markup/tty|tootcat@tootcat:~/web/mastodon$ yarn install --pure-lockfile}} :: This also seemed successful, but it also asked me to upgrade Yarn with these specific commands: : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm upgrade --global yarn}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm rebuild node-sass}} <pre> > node-sass@4.7.2 install /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/install.js node-sass build Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node > node-sass@4.7.2 postinstall /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/build.js Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node Testing binary Binary is fine node-sass@4.7.2 /home/tootcat/web/mastodon/node_modules/node-sass </pre> ...and then we move on to configuring Postgres (already done) and nginx, which I think I should add as step 5. ===step 5: configure nginx=== 27617e1d96aafb4e19381f539f3ea94c9283c5c8 565 564 2018-01-15T00:02:37Z Woozle 1 wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # configure nginx # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. * [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md Instructions] wanted to configure nginx after installing Mastodon, and this did need to be looked into at some point, so added it as step 5. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} Skipping the bit about installing Ruby, since that is already installed on this server. chdir to <code>/home/tootcat/web</code>, then: : {{markup/tty|tootcat@tootcat:~/web$| git clone https://github.com/tootsuite/mastodon.git mastodon}} :: {{markup/tty|Cloning into 'mastodon'...}} :: {{markup/tty|remote: Counting objects: 56389, done.}} :: {{markup/tty|remote: Compressing objects: 100% (13/13), done.}} :: {{markup/tty|remote: Total 56389 (delta 0), reused 3 (delta 0), pack-reused 56376}} :: {{markup/tty|Receiving objects: 100% (56389/56389), 52.51 MiB | 30.41 MiB/s, done.}} :: {{markup/tty|Resolving deltas: 100% (37140/37140), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon/}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)}} :: {{markup/tty|Note: checking out 'v2.1.3'.}} :: <pre>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 35b8498... Skip ActivityPub Announces of non-public objects (#6230)</pre> : {{markup/tty|tootcat@tootcat:~/web/mastodon$| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|ERROR: While executing gem ... (Gem::FilePermissionError)}} :: {{markup/tty| You don't have write permissions for the /var/lib/gems/2.3.0 directory.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle exec rails c}} :: {{markup/tty/color|red|Could not find rake-12.3.0 in any of the sources}} :: {{markup/tty/color|orange|Run `bundle install` to install missing gems.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install}} :: {{markup/tty/color|orange|Warning: the running version of Bundler (1.15.3) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.}} :: {{markup/tty|Fetching gem metadata from https://rubygems.org/...........}} :: {{markup/tty|Fetching version metadata from https://rubygems.org/...}} :: {{markup/tty|Fetching dependency metadata from https://rubygems.org/..}} :: {{markup/tty|Fetching rake 12.3.0}} <pre> Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run: bundle install --path vendor/bundle to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo. Password: </pre> Decided this was not the way to do it, and logged in as root: : {{markup/tty|root@tootcat:~#| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|Successfully installed bundler-1.16.1}} :: {{markup/tty|Parsing documentation for bundler-1.16.1}} :: {{markup/tty|Installing ri documentation for bundler-1.16.1}} :: {{markup/tty|Done installing documentation for bundler after 9 seconds}} :: {{markup/tty|1 gem installed}} : {{markup/tty|root@tootcat:~#| bundle install --deployment --without development test}} :: {{markup/tty/color|orange|Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.}} :: {{markup/tty/color|red|Could not locate Gemfile}} Okay, so I guess it's back to the mastodon user... : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install --deployment --without development test}} :: This seemed to work: [[/paste/2018/01/14/01]] : {{markup/tty|tootcat@tootcat:~/web/mastodon$ yarn install --pure-lockfile}} :: This also seemed successful, but it also asked me to upgrade Yarn with these specific commands: : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm upgrade --global yarn}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm rebuild node-sass}} <pre> > node-sass@4.7.2 install /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/install.js node-sass build Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node > node-sass@4.7.2 postinstall /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/build.js Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node Testing binary Binary is fine node-sass@4.7.2 /home/tootcat/web/mastodon/node_modules/node-sass </pre> ...and then we move on to configuring Postgres (already done) and nginx, which I think I should add as step 5. ===step 5: configure nginx - ABANDONED for now=== I made a copy of /etc/nginx/sites-available/default and called it toot-cat-new, then changed just a couple of things: * The '''server_name''' was changed from <code>toot.cat</code> to <code>new.toot.cat</code> in two places. ...and then I realized that this plan was going to require setting up extra instances of Puma and the media server (name?) on different ports from 3000 and 4000... which I think I know how to do, but this kinda crosses a threshold into territory uncertain enough that I decided to let a professional do it this time, and live to fight another day. 32a528d6ee58c3f61835830e1668de3dbab8c736 566 565 2018-01-15T11:57:20Z Woozle 1 Woozle moved page [[User:Woozle/toot.cat]] to [[User:Woozle/toot.cat/2018/01/14]]: this was one set of things wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # configure nginx # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. * [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md Instructions] wanted to configure nginx after installing Mastodon, and this did need to be looked into at some point, so added it as step 5. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} Skipping the bit about installing Ruby, since that is already installed on this server. chdir to <code>/home/tootcat/web</code>, then: : {{markup/tty|tootcat@tootcat:~/web$| git clone https://github.com/tootsuite/mastodon.git mastodon}} :: {{markup/tty|Cloning into 'mastodon'...}} :: {{markup/tty|remote: Counting objects: 56389, done.}} :: {{markup/tty|remote: Compressing objects: 100% (13/13), done.}} :: {{markup/tty|remote: Total 56389 (delta 0), reused 3 (delta 0), pack-reused 56376}} :: {{markup/tty|Receiving objects: 100% (56389/56389), 52.51 MiB | 30.41 MiB/s, done.}} :: {{markup/tty|Resolving deltas: 100% (37140/37140), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon/}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)}} :: {{markup/tty|Note: checking out 'v2.1.3'.}} :: <pre>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 35b8498... Skip ActivityPub Announces of non-public objects (#6230)</pre> : {{markup/tty|tootcat@tootcat:~/web/mastodon$| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|ERROR: While executing gem ... (Gem::FilePermissionError)}} :: {{markup/tty| You don't have write permissions for the /var/lib/gems/2.3.0 directory.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle exec rails c}} :: {{markup/tty/color|red|Could not find rake-12.3.0 in any of the sources}} :: {{markup/tty/color|orange|Run `bundle install` to install missing gems.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install}} :: {{markup/tty/color|orange|Warning: the running version of Bundler (1.15.3) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.}} :: {{markup/tty|Fetching gem metadata from https://rubygems.org/...........}} :: {{markup/tty|Fetching version metadata from https://rubygems.org/...}} :: {{markup/tty|Fetching dependency metadata from https://rubygems.org/..}} :: {{markup/tty|Fetching rake 12.3.0}} <pre> Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run: bundle install --path vendor/bundle to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo. Password: </pre> Decided this was not the way to do it, and logged in as root: : {{markup/tty|root@tootcat:~#| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|Successfully installed bundler-1.16.1}} :: {{markup/tty|Parsing documentation for bundler-1.16.1}} :: {{markup/tty|Installing ri documentation for bundler-1.16.1}} :: {{markup/tty|Done installing documentation for bundler after 9 seconds}} :: {{markup/tty|1 gem installed}} : {{markup/tty|root@tootcat:~#| bundle install --deployment --without development test}} :: {{markup/tty/color|orange|Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.}} :: {{markup/tty/color|red|Could not locate Gemfile}} Okay, so I guess it's back to the mastodon user... : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install --deployment --without development test}} :: This seemed to work: [[/paste/2018/01/14/01]] : {{markup/tty|tootcat@tootcat:~/web/mastodon$ yarn install --pure-lockfile}} :: This also seemed successful, but it also asked me to upgrade Yarn with these specific commands: : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm upgrade --global yarn}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm rebuild node-sass}} <pre> > node-sass@4.7.2 install /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/install.js node-sass build Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node > node-sass@4.7.2 postinstall /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/build.js Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node Testing binary Binary is fine node-sass@4.7.2 /home/tootcat/web/mastodon/node_modules/node-sass </pre> ...and then we move on to configuring Postgres (already done) and nginx, which I think I should add as step 5. ===step 5: configure nginx - ABANDONED for now=== I made a copy of /etc/nginx/sites-available/default and called it toot-cat-new, then changed just a couple of things: * The '''server_name''' was changed from <code>toot.cat</code> to <code>new.toot.cat</code> in two places. ...and then I realized that this plan was going to require setting up extra instances of Puma and the media server (name?) on different ports from 3000 and 4000... which I think I know how to do, but this kinda crosses a threshold into territory uncertain enough that I decided to let a professional do it this time, and live to fight another day. 32a528d6ee58c3f61835830e1668de3dbab8c736 10 177 576 2018-01-14T20:08:38Z Woozle 1 Created page with "<code>{{faint|{{{1}}}}}<span style="color:green; font-weight:bold;">{{{2}}}</span></code>" wikitext text/x-wiki <code>{{faint|{{{1}}}}}<span style="color:green; font-weight:bold;">{{{2}}}</span></code> a835b5d344b09c84e168c0d1fd102500ca48bf91 577 576 2018-01-14T20:22:42Z Woozle 1 wikitext text/x-wiki <code>{{faint|{{{1}}}}}<span style="color:green; font-weight:bold;">{{{2|}}}</span></code> 32d030796941c97ed9d9e1618db8974687733031 10 178 579 2018-01-14T22:50:12Z Woozle 1 Created page with "<code style="color:{{{1}}}">{{{2}}}</code>" wikitext text/x-wiki <code style="color:{{{1}}}">{{{2}}}</code> a8340135190b70537603ddb32f2ac05702993d9f 0 174 552 2018-01-15T11:59:19Z Woozle 1 Created page with "Response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the..." wikitext text/x-wiki Response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the launch of V5). Domains are fully imported only if the owner account has been migrated too. Domains for which the migrated account is only Administrative, Technical and/or Billing contact are partially imported under an Organization with limited permissions (or need to be synchronized to be displayed). Domain "toot.cat" has another "classic" account as owner (and need synchronization) that's why it was not displayed. No it appears under an organization named "BS10413-GANDI" which is in fact the Owner 'classic' handle. To get full rights on the domain you will have to ask the owner to migrate his account to V5, or you will have to migrate the owner account and merge it with your current V5 account. For this case go to the "Classic" interface to verify you have access to this account (password mostly) and verify that the email address and legal informations (Name or company name, account type) match exactly the ones for your account and or organization. If this is not the case you will have to make "change owner account" operation to a new 'classic' handle with the correct informations. http://wiki.gandi.net/en/contacts/changeowner A change of owner mean the validation of an email sent to the email address registered for each of the owner. I invite you to verify specifically that the email addresses fo the owners are correct, valid and that no Anti Spam or Whois privacy service is activated. This operation is just an administrative one, and there would be no impact on the running of the domains or their services. Only domains can be "moved" from one account to another. Other products like SSL certificates, websites or hosting are "locked" to the account which create them. Then go to V5 and log out of the V5 account. Then log in using the classic handle (complete BS10413-GANDI) and password, to trigger the migration process. You can find more information on our new V5 interface at this address: https://doc.gandi.net/en# Do not hesitate to contact us if you need more information. Our best wishes for a happy and successful New Year. Best regards <pre> \o/ Thierry G http://v4.gandi.net/ ------------------------------------------------------------------------------- Are you satisfied with the quality of the reply you received? YES: https://v4.gandi.net/faq/feedback/yes NO: https://v4.gandi.net/faq/feedback/no no I would like to give more detailed feedback: https://v4.gandi.net/faq/feedback. ------------------------------------------------------------------------------- </pre> </blockquote> 4065d27ee6887a1833b9aff000c4d475e12ebd82 553 552 2018-01-15T12:11:25Z Woozle 1 wikitext text/x-wiki My original request on Jan. 11: <blockquote> How do I move toot.cat out of the "BS10413-GANDI" sub-account (which I did not create, and which has "limited permissions" that I don't see how to edit) and into my main account ("woozle", the one I am writing from) so that I can manage DNS and automatic renewals? Thank you. </blockquote> In the meantime, I ''did'' figure out how to adjust the DNS, so this only becomes a crisis when I need to renew the domain. Four days later, here's the response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the launch of V5). Domains are fully imported only if the owner account has been migrated too. Domains for which the migrated account is only Administrative, Technical and/or Billing contact are partially imported under an Organization with limited permissions (or need to be synchronized to be displayed). Domain "toot.cat" has another "classic" account as owner (and need synchronization) that's why it was not displayed. No it appears under an organization named "BS10413-GANDI" which is in fact the Owner 'classic' handle. To get full rights on the domain you will have to ask the owner to migrate his account to V5, or you will have to migrate the owner account and merge it with your current V5 account. For this case go to the "Classic" interface to verify you have access to this account (password mostly) and verify that the email address and legal informations (Name or company name, account type) match exactly the ones for your account and or organization. If this is not the case you will have to make "change owner account" operation to a new 'classic' handle with the correct informations. http://wiki.gandi.net/en/contacts/changeowner A change of owner mean the validation of an email sent to the email address registered for each of the owner. I invite you to verify specifically that the email addresses fo the owners are correct, valid and that no Anti Spam or Whois privacy service is activated. This operation is just an administrative one, and there would be no impact on the running of the domains or their services. Only domains can be "moved" from one account to another. Other products like SSL certificates, websites or hosting are "locked" to the account which create them. Then go to V5 and log out of the V5 account. Then log in using the classic handle (complete BS10413-GANDI) and password, to trigger the migration process. You can find more information on our new V5 interface at this address: https://doc.gandi.net/en# Do not hesitate to contact us if you need more information. Our best wishes for a happy and successful New Year. Best regards <pre> \o/ Thierry G http://v4.gandi.net/ ------------------------------------------------------------------------------- Are you satisfied with the quality of the reply you received? YES: https://v4.gandi.net/faq/feedback/yes NO: https://v4.gandi.net/faq/feedback/no no I would like to give more detailed feedback: https://v4.gandi.net/faq/feedback. ------------------------------------------------------------------------------- </pre> </blockquote> OMFG what?? 2bb02c89dddfaf9342bf98b69758a3b374a91076 554 553 2018-01-15T12:32:53Z Woozle 1 possible registrars wikitext text/x-wiki My original request on Jan. 11: <blockquote> How do I move toot.cat out of the "BS10413-GANDI" sub-account (which I did not create, and which has "limited permissions" that I don't see how to edit) and into my main account ("woozle", the one I am writing from) so that I can manage DNS and automatic renewals? Thank you. </blockquote> In the meantime, I ''did'' figure out how to adjust the DNS, so this only becomes a crisis when I need to renew the domain. Four days later, here's the response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the launch of V5). Domains are fully imported only if the owner account has been migrated too. Domains for which the migrated account is only Administrative, Technical and/or Billing contact are partially imported under an Organization with limited permissions (or need to be synchronized to be displayed). Domain "toot.cat" has another "classic" account as owner (and need synchronization) that's why it was not displayed. No it appears under an organization named "BS10413-GANDI" which is in fact the Owner 'classic' handle. To get full rights on the domain you will have to ask the owner to migrate his account to V5, or you will have to migrate the owner account and merge it with your current V5 account. For this case go to the "Classic" interface to verify you have access to this account (password mostly) and verify that the email address and legal informations (Name or company name, account type) match exactly the ones for your account and or organization. If this is not the case you will have to make "change owner account" operation to a new 'classic' handle with the correct informations. http://wiki.gandi.net/en/contacts/changeowner A change of owner mean the validation of an email sent to the email address registered for each of the owner. I invite you to verify specifically that the email addresses fo the owners are correct, valid and that no Anti Spam or Whois privacy service is activated. This operation is just an administrative one, and there would be no impact on the running of the domains or their services. Only domains can be "moved" from one account to another. Other products like SSL certificates, websites or hosting are "locked" to the account which create them. Then go to V5 and log out of the V5 account. Then log in using the classic handle (complete BS10413-GANDI) and password, to trigger the migration process. You can find more information on our new V5 interface at this address: https://doc.gandi.net/en# Do not hesitate to contact us if you need more information. Our best wishes for a happy and successful New Year. Best regards <pre> \o/ Thierry G http://v4.gandi.net/ ------------------------------------------------------------------------------- Are you satisfied with the quality of the reply you received? YES: https://v4.gandi.net/faq/feedback/yes NO: https://v4.gandi.net/faq/feedback/no no I would like to give more detailed feedback: https://v4.gandi.net/faq/feedback. ------------------------------------------------------------------------------- </pre> </blockquote> OMFG what?? I'm thinking it may just be best to get the domain back out of that hellhole, after taking some time to research a better home for it (now that the need is no longer urgent). Possibilities include: * [http://hover.com Hover] (where PolymerWitch originally registered it) * [http://portfast.co.uk portfast.co.uk] ([https://witches.town/@lambdagrrl/99353801843467099 recommendation]) b212fa6f199515e59d6a518734cd5fd3e543184e 0 1 1 2018-03-29T23:52:16Z MediaWiki default 0 wikitext text/x-wiki <strong>MediaWiki has been installed.</strong> Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki] 5702e4d5fd9173246331a889294caf01a3ad3706 9 1 2018-03-30T10:38:29Z Woozle 1 wikitext text/x-wiki <center> =Welcome to '''Me'''{{grey|dia}}'''W'''{{grey|iki}}!= </center> ==Purpose== This wiki is a compromise. There are some [[/wishlist|specific tools]] I wanted to have in place, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs anchors &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and exploring/modeling methods of doing that. 161565f4a312aa5f47a98341a0a06d57f29137e4 21 9 2018-03-30T18:26:22Z Woozle 1 wikitext text/x-wiki <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a wiki<ref name=other /> for the Mastodon community, with a focus on helping people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other].</ref> </references> 1faee0e9ed13387ef628bdecb9d050f1be8fc10e 27 21 2018-04-02T18:53:40Z Woozle 1 wikitext text/x-wiki <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a wiki<ref name=other /> for the Mastodon community, with a focus on helping people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Mastodon News== * '''2018-04-02''' {{ls/domain|witches.town}} is [https://witches.town/@TheSupreme/99760206680527013 apparently] shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other].</ref> </references> 03d8d084ae49df532b0b4fbcc10f6ea7e9bffbf7 8 2 2 2018-03-30T00:06:59Z Woozle 1 Created page with " * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|Help:Main * SEARCH * TOOLBOX * LANGUAGES" wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|Help:Main * SEARCH * TOOLBOX * LANGUAGES 41d4f07a2b08db407c040b1821146e32b340c11b 3 2 2018-03-30T00:07:13Z Woozle 1 wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** Help:Main|help * SEARCH * TOOLBOX * LANGUAGES b7fb2bc0de424ea780011c382b0f1ce90ebb7679 12 3 4 2018-03-30T00:08:02Z Woozle 1 Created page with "More help stuff needs to go here, but for now... * [[Help:Admin]]: site administration help" wikitext text/x-wiki More help stuff needs to go here, but for now... * [[Help:Admin]]: site administration help 4b66f14f9b33de91ce499fbeba5caa44f717c3d9 12 4 5 2018-03-30T00:08:19Z Woozle 1 Created page with "This page is help information for site administrators. * [[mediawiki:sidebar]]: contents of the navigation column on the left * [[MediaWiki:Common.css]]: CSS to apply to all..." wikitext text/x-wiki This page is help information for site administrators. * [[mediawiki:sidebar]]: contents of the navigation column on the left * [[MediaWiki:Common.css]]: CSS to apply to all pages a785a737b9e6d021e4f7bfccee1109afe0992c26 2 5 6 2018-03-30T10:31:21Z Woozle 1 Created page with "I'm not sure what Megan's deal is, but she took made claims which instigated yet another pile-on against Ginny McQueen and then refused to provide evidence. All times are EST..." wikitext text/x-wiki I'm not sure what Megan's deal is, but she took made claims which instigated yet another pile-on against Ginny McQueen and then refused to provide evidence. All times are EST; not sure where Megan lives. I was alerted to this problem by a [https://toot.cat/web/statuses/99769105144973401 private post]. ==2018-03-29== ===[https://octodon.social/@Megan/99768831066068963 15:25] from Megan=== I have first hand contact with the trans women who say she sexually abused them, phone calls, emails and DMs starting in January 2014. I've had their first hand accounts from them and I believe them. Am I going to pass them on to you. Fuck that noise, I'm blocking her, you and everyone who defends her. Whatever happens down the line from here, you share culpability in. And if you arent a trans woman, stay the fuck out of this fight. https://kitty.town/@GinnyMcQueen/99768588355313726 ===[https://toot.cat/@woozle/99769209394684635 17:02] from me=== '''CW:''' claims of abuse @Megan &lt;raises hand&gt; Transwoman here. Can you tell me what this is about? Are they saying that *Ginny* abused them, or someone else did? It's not clear to me from what you've said or why Ginny is being involved. Thanks. ===[https://octodon.social/@Megan/99769257187135510 17:14] from Megan=== @woozle The first part is where I explained my first hand contact with Laurelai Baileys victims, the ones who said she raped them. The link to Ginny is because she is defending Laurelai as victim of a smear campaign which I can state is, in the case of the rape claims, false, the trans women she abused are real. I spoke to them AT THE TIME they made their accusations. Laurelai is an accomplished liar and extremely manipulative. Now please, leave me alone as per my request. ===[https://toot.cat/@woozle/99769312753623401 17:28] from me=== @Megan I will leave you alone -- sorry about that -- but I'm not going to believe secondhand accusations.. and you kind of threw yourself in the middle of this by directing people at Ginny. If you want to be left alone, I recommend deleting that toot -- feel free to replace it with one that suggests people contact me instead. Thanks. ===[https://octodon.social/@Megan/99769335180646246 17:34] from Megan=== '''CW:''' claims of abuse @woozle Do not ever tell me how to conduct myself on the subject of discussing a rapist whose victims I have had personal experience of supoorting. You are blocked. ----- She did in fact block me at that point. 920ab97d0b43d3dd23fc63d6176637c627d40199 19 6 2018-03-30T11:47:03Z Woozle 1 screenshot wikitext text/x-wiki I'm not sure what Megan's deal is, but she took made claims which instigated yet another pile-on against Ginny McQueen and then refused to provide evidence. All times are EST; not sure where Megan lives. I was alerted to this problem by a [https://toot.cat/web/statuses/99769105144973401 private post]. [[File:Screenshot-2018-3-30 Megan@octodon.social.png|thumb|screenshot of the dialogue]] ==2018-03-29== ===[https://octodon.social/@Megan/99768831066068963 15:25] from Megan=== I have first hand contact with the trans women who say she sexually abused them, phone calls, emails and DMs starting in January 2014. I've had their first hand accounts from them and I believe them. Am I going to pass them on to you. Fuck that noise, I'm blocking her, you and everyone who defends her. Whatever happens down the line from here, you share culpability in. And if you arent a trans woman, stay the fuck out of this fight. https://kitty.town/@GinnyMcQueen/99768588355313726 ===[https://toot.cat/@woozle/99769209394684635 17:02] from me=== '''CW:''' claims of abuse @Megan &lt;raises hand&gt; Transwoman here. Can you tell me what this is about? Are they saying that *Ginny* abused them, or someone else did? It's not clear to me from what you've said or why Ginny is being involved. Thanks. ===[https://octodon.social/@Megan/99769257187135510 17:14] from Megan=== @woozle The first part is where I explained my first hand contact with Laurelai Baileys victims, the ones who said she raped them. The link to Ginny is because she is defending Laurelai as victim of a smear campaign which I can state is, in the case of the rape claims, false, the trans women she abused are real. I spoke to them AT THE TIME they made their accusations. Laurelai is an accomplished liar and extremely manipulative. Now please, leave me alone as per my request. ===[https://toot.cat/@woozle/99769312753623401 17:28] from me=== @Megan I will leave you alone -- sorry about that -- but I'm not going to believe secondhand accusations.. and you kind of threw yourself in the middle of this by directing people at Ginny. If you want to be left alone, I recommend deleting that toot -- feel free to replace it with one that suggests people contact me instead. Thanks. ===[https://octodon.social/@Megan/99769335180646246 17:34] from Megan=== '''CW:''' claims of abuse @woozle Do not ever tell me how to conduct myself on the subject of discussing a rapist whose victims I have had personal experience of supoorting. You are blocked. ----- She did in fact block me at that point. 413c7f5f9ca2c89adac3a184afaa40559e527d6e 2 6 7 2018-03-30T10:31:28Z Woozle 1 Created page with "==Dialogues== * [[/octodon.social/@Megan]]" wikitext text/x-wiki ==Dialogues== * [[/octodon.social/@Megan]] 8a8df7b09f1acfde8965d0f91e33bea2e5eeae33 10 7 8 2018-03-30T10:38:10Z Woozle 1 Created page with "<span style="color: #888;">{{{1}}}</span>" wikitext text/x-wiki <span style="color: #888;">{{{1}}}</span> 01b5762b3a6230a8fd38f31b0036886392ad9c53 10 8 10 2018-03-30T10:50:44Z Woozle 1 Created page with "[[User:{{{1}}}|{{{1}}}]]" wikitext text/x-wiki [[User:{{{1}}}|{{{1}}}]] 2363afc626c2c3d0eb41fd3490e04b7fa1f2bb29 11 10 2018-03-30T10:51:19Z Woozle 1 Woozle moved page [[Template:Lu/woozle]] to [[Template:Lu]] without leaving a redirect: oopsy wikitext text/x-wiki [[User:{{{1}}}|{{{1}}}]] 2363afc626c2c3d0eb41fd3490e04b7fa1f2bb29 10 9 12 2018-03-30T10:52:14Z Woozle 1 Created page with "[https://{{{1}}} {{{1}}}]" wikitext text/x-wiki [https://{{{1}}} {{{1}}}] 3f543809be6ec6bb318d028759d0253c267a743c 4 10 13 2018-03-30T11:08:08Z Woozle 1 Created page with "==Basics== * '''Ownership''': Mew is operated and hosted by {{lu|woozle}}, sysadmin of {{ls/domain|toot.cat}} (hopefully soon to be joined by a team of others from across the..." wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lu|woozle}}, sysadmin of {{ls/domain|toot.cat}} (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any information you enter on Mew (including, notably, your email address if you enter one on your profile) will be accessible to the server sysop (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki) unless you make ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. ffa8df0e932217b05faf69f57d3598f3843bda5c 14 13 2018-03-30T11:12:31Z Woozle 1 Sentence finished, and one more thing wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lu|woozle}}, sysadmin of {{ls/domain|toot.cat}} (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any profile information you enter on Mew (including, notably, your email address) will be accessible to database sysops (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki). * '''Warrant Canary''': in the event of a subpoena, we will follow our conscience as regards how much to reveal both to authorities and to the community. We have not received any such requests as of this writing, and (at a minimum) this sentence will be removed in the event that we do. ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. 73c2e320022f8d35e22da0f534263d2b20da0532 20 14 2018-03-30T12:05:28Z Woozle 1 wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lu|woozle}}, sysadmin of {{ls/domain|toot.cat}} (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any profile information you enter on Mew (including, notably, your email address) will be accessible to database sysops (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki). * '''Warrant Canary''': in the event of a subpoena, we will follow our conscience as regards how much to reveal both to authorities and to the community. We have not received any such requests as of this writing, and (at a minimum) this sentence will be removed in the event that we do. ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. ==History== * '''2018-03-30''' (Fri) Installed MediaWiki last night and got it mostly configured; got image uploads working and some explanatory content; still trying to figure out a good way to have some pages public and most pages not. ecf05337d2e9bc0850dd1c97ddca0203fa8d5633 23 20 2018-03-31T10:37:19Z Woozle 1 link changes wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lpub/user|woozle}}, sysadmin of [[toot.cat]] (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any profile information you enter on Mew (including, notably, your email address) will be accessible to database sysops (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki). * '''Warrant Canary''': in the event of a subpoena, we will follow our conscience as regards how much to reveal both to authorities and to the community. We have not received any such requests as of this writing, and (at a minimum) this sentence will be removed in the event that we do. ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. ==History== * '''2018-03-30''' (Fri) Installed MediaWiki last night and got it mostly configured; got image uploads working and some explanatory content; still trying to figure out a good way to have some pages public and most pages not. efec0fde80a897c6b912d207a65472aece4cd295 6 13 18 2018-03-30T11:44:52Z Woozle 1 [[category:screenshots]] * '''what''': screenshot of [[User:Woozle/octodon.social/@Megan|a dialogue]] wikitext text/x-wiki [[category:screenshots]] * '''what''': screenshot of [[User:Woozle/octodon.social/@Megan|a dialogue]] 71ab15f870c448ff28e7cf4b033abdbb1d697c6d 10 14 22 2018-03-31T10:36:41Z Woozle 1 Created page with "[[pub/user/{{{1}}}|{{{1}}}]]" wikitext text/x-wiki [[pub/user/{{{1}}}|{{{1}}}]] 5134ca0ddd9b0b95f42bc8bb78b7b80f548ebeab 10 15 24 2018-04-01T15:35:24Z Woozle 1 Created page with "{{pub/{{{1}}}|{{{1}}}}}" wikitext text/x-wiki {{pub/{{{1}}}|{{{1}}}}} a54cb8ecb5742258d00f281e015e2483277b9683 25 24 2018-04-01T15:35:55Z Woozle 1 oops, I meant... wikitext text/x-wiki [[pub/{{{1}}}|{{{1}}}]] 043ae8dd3ddf08373a63a0999f52d8b5148b2636 0 16 26 2018-04-01T15:37:09Z Woozle 1 Created page with "I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's proba..." wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. 263a4ab2f02593c44e28ae3aaf3e45e057b61336 6 17 28 2018-04-02T21:57:31Z Woozle 1 [[category:screenshots]] wikitext text/x-wiki [[category:screenshots]] fd2a1dc4a2c7dc38b590f937cbd6d4fa3a54f6aa 0 18 29 2018-04-02T21:59:26Z Woozle 1 Created page with "'''witches.town''' is still, as of this writing, a Mastodon instance. The sysop has announced that she will be shutting down the service on 2018-04-30. They had been a somewha..." wikitext text/x-wiki '''witches.town''' is still, as of this writing, a Mastodon instance. The sysop has announced that she will be shutting down the service on 2018-04-30. They had been a somewhat quirky instance (e.g. the limit for toots is 666 rather than the standard 500, and special symbols were apparently given to users with exactly 666 followers) with a very loyal membership. The sysop stated that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but would not say why. ==Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] *** @Alda is or was an admin on witches.town<ref name=profile1 />; not sure what the relationship is, but this toot evidently played a large part in what happened. ==Footnote== <references> <ref name=profile1>[[:File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|@TheSupreme@witches.town follow list]], retrieved 2018-04-02 17:58</ref> </references> f715426b45a986373242addb83b9455804fdab34 31 29 2018-04-02T22:20:36Z Woozle 1 wikitext text/x-wiki [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. @TheSupreme@witches.town, sysop of the instance, announced on 2018-04-02 that she will be shutting down the service on 2018-04-30. WT had been a somewhat quirky instance (e.g. the limit for toots is 666 characters rather than the standard 500, and special symbols were apparently given to users with exactly 666 followers) with a very loyal membership. This followed an earlier [https://witches.town/@TheSupreme/99757948217405250 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://witches.town/@TheSupreme/99760206680527013 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The April 2 announcement was followed up by a [https://witches.town/@TheSupreme/99790761655634428 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] 3b691b75eb15a205bc2782f7012bc1e489e5422c 35 31 2018-04-03T00:10:14Z Woozle 1 replacing witches.town links with toot.cat links so they won't go away; some reorganization wikitext text/x-wiki [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. WT had been a somewhat quirky instance (e.g. the limit for toots is 666 characters rather than the standard 500, and special symbols were apparently given to users with exactly 666 followers) with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99757948365320502 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) e7475e52be1795609060c8218a2a36170f6d75f4 36 35 2018-04-03T09:43:03Z Woozle 1 phrasing tweak wikitext text/x-wiki [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99757948365320502 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) 90829c4045ab3939c8c4a7b29900fe48af9ea8be 50 36 2018-04-20T12:01:04Z Woozle 1 catg wikitext text/x-wiki [[category:Mastodon instances]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99757948365320502 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) 0c2c3354757d098089257d2663f5448db8126f78 63 50 2018-04-30T11:02:50Z Woozle 1 survey wikitext text/x-wiki [[category:Mastodon instances]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99757948365320502 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] e62b23c731d6dd0b32710f91dc7d471d664f0d54 66 63 2018-04-30T11:29:44Z Woozle 1 wikitext text/x-wiki [[category:Mastodon instances]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99757948365320502 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 52c441563a3789c3b9f99bf31e58a34808e6a5ed 6 17 30 28 2018-04-02T22:02:28Z Woozle 1 wikitext text/x-wiki [[category:screenshots]] Could not archive page text due to robots.txt (probably standard for Mastodon) 82502d7f37c9f87afbb92ed6edb7f36b6ea96698 0 1 32 27 2018-04-02T22:21:11Z Woozle 1 /* Mastodon News */ wikitext text/x-wiki <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a wiki<ref name=other /> for the Mastodon community, with a focus on helping people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Mastodon News== * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other].</ref> </references> 11d81f0baa7b182a0b60464b026ba282558b2ef7 34 32 2018-04-02T22:43:35Z Woozle 1 clarifying language, I hope? wikitext text/x-wiki <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Mastodon News== * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> f167c7a9e7b895c3340e284be6f24a467e7dfb0a 53 34 2018-04-27T00:32:56Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin ==Mastodon News== * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 0eca776f5fd3e9e8a4baa2ab0c7d6b2a9d938c13 57 53 2018-04-27T18:59:42Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin ==Mastodon News== * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> d0fd0083c9e5eac98bb4f858cc970d1c62edab95 61 57 2018-04-30T10:54:56Z Woozle 1 cutie.space wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin ==Mastodon News== * '''2018-04-30''' Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 2b9d0ab03e98a01b004ad6be1c984ade50e4663d 62 61 2018-04-30T10:57:41Z Woozle 1 /* Mastodon News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin ==Mastodon News== * '''2018-04-30''' Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> ceb65b1417660cf98c3ced36584b472f8b0b6687 67 62 2018-05-01T10:40:12Z Woozle 1 news updates wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 50afa6233bbe80e78275e7132af7508bb80ba0b9 4 19 33 2018-04-02T22:38:19Z Woozle 1 Created page with "==Tools== * a way to authenticate via Mastodon, preferably checked against the blocklists of a set of trusted users There was more, but I can't think of it at the moment. ==A..." wikitext text/x-wiki ==Tools== * a way to authenticate via Mastodon, preferably checked against the blocklists of a set of trusted users There was more, but I can't think of it at the moment. ==Aesthetic== * would be nice to match Mastodon's default look-and-feel, at least as an option (MW does let users choose skins) 187b7346e8af4d901c2f1fcc62efc6a1bfad8ba7 37 33 2018-04-03T10:41:27Z Woozle 1 wikitext text/x-wiki ==Tools== * a way to authenticate via Mastodon, preferably checked against the blocklists of a set of trusted users ** ...or a Mastobot from which Masto users could request an account (which would then automatically create a MeW account defaulting to their username and, if available, email address) * more fine-grained security: I should be able to define groups and then give them read/write privileges to certain areas to which they wouldn't otherwise have access ** MediaWiki really wasn't built for this; I'm working on my own wiki software. There was more, but I can't think of it at the moment. ==Aesthetic== * would be nice to match Mastodon's default look-and-feel, at least as an option (MW does let users choose skins) 346c7989517f9f07aa3cc9274edbc0c9d24cf19d 2 6 39 7 2018-04-04T20:24:25Z Woozle 1 wikitext text/x-wiki ==Situations== * [[witches.town]] ==Dialogues== * [[/octodon.social/@Megan]] 5c8247d3ddf70818edfc90404ac5f25e3cf2068c 10 21 40 2018-04-04T20:26:25Z Woozle 1 Created page with "'''{{{1}}}''' [[/{{#sub:{{{1}}}|0|4}}/{{#sub:{{{1}}}|5|2}}/{{#sub:{{{1}}}|8|2}}/{{{2}}}|{{{2}}}]]" wikitext text/x-wiki '''{{{1}}}''' [[/{{#sub:{{{1}}}|0|4}}/{{#sub:{{{1}}}|5|2}}/{{#sub:{{{1}}}|8|2}}/{{{2}}}|{{{2}}}]] fd5578ae7275d1e7a215cd5e3973669492a7cf1e 0 22 41 2018-04-04T21:56:19Z Woozle 1 Created page with "<big> : ''I strive to evaluate first in terms of potential harm.'' : ''I strive to keep my emotions on hold until I have all the facts.'' </big> I'm working towards a redesign..." wikitext text/x-wiki <big> : ''I strive to evaluate first in terms of potential harm.'' : ''I strive to keep my emotions on hold until I have all the facts.'' </big> I'm working towards a redesigned process of justice. What I've come up with isn't as radically revisioned as what I'd like to do in the long run, but I don't have the tools for that yet. Traditional justice systems are usually based on hierarchies &ndash; something that has harmed many of us and which I believe most of us want to move away from. Justice should empower us all equally. Ideally, a system of justice would rely more on rallying our common sense of empathy<ref name=sydney /> to create the authority necessary to exercise power against malicious acts. To do that, we need tools that let us nurture and empower empathy, and disempower selfishness. We're not there yet. What we do have now is: * a fediverse, with a very simple and fairly short hierarchy: instance admins on the upper layer and regular users on the lower, with relatively minor and variable differences in power on each level, and * this wiki, in which I hope we can build a copyable navigation aid for uncertain waters &ndash; a reference index, a catalog of findable landmarks. It has fallen naturally to the instance admins to administer justice &ndash; and yet we barely have the seeds of a set of best practices. We've done well crafting our Codes of Conduct to define the responsibilities of our users &ndash; but recent events have shown that we need Codes of Justice, to define (and limit) the responsibilities of our admins. Power must be accountable, and must be earned through its use in the service of the disempowered<ref name=banazi /> or else it is illegitimate. A Code of Justice needs to be able to answer certain questions: * As a user, how can I seek redress for harm done to me? * As an admin &mdash; ** under what circumstances am I enabled to act? ** under what circumstances do I have some moral obligation to act? ** what are the limits of the actions I may take? ''writing in progress'' ==Footnotes== <references> <ref name=sydney>Apparently I now have a Sydney head-squirrel because I'm hearing strenuous objections to the idea that we could ever rely on any such thing, especially not now, and she's really quite skeptical that such a thing really exists in the first place, so the idea of depending on it for our safety is really kind of hecking scary. I'm... not ignoring her, but deferring that discussion for a later time; my statement was speculative and I agree we're not ready to go there yet.</ref> <ref name=banazi>This is essentially why we penalize instances that enable right-wing propaganda: they are failing in their service to the disempowered. They fail to protect the weak from the strength of induced collective hostility.</ref> </references> 224037261c47a83a146731b7fa0b49e281bb58bf 42 41 2018-04-05T19:07:44Z Woozle 1 I guess this is finished? wikitext text/x-wiki <big> : ''I strive to evaluate first in terms of potential harm.'' : ''I strive to keep my emotions on hold until I have all the facts.'' </big> I'm working towards a redesigned process of justice. What I've come up with isn't as radically revisioned as what I'd like to do in the long run, but I don't have the tools for that yet. Traditional justice systems are usually based on hierarchies &ndash; something that has harmed many of us and which I believe most of us want to move away from. Justice should empower us all equally. Ideally, a system of justice would rely more on rallying our common sense of empathy<ref name=sydney /> to create the authority necessary to exercise power against malicious acts. To do that, we need tools that let us nurture and empower empathy, and disempower selfishness. We're not there yet. What we do have now is: * a fediverse, with a very simple and fairly short hierarchy: instance admins on the upper layer and regular users on the lower, with relatively minor and variable differences in power on each level, and * this wiki, in which I hope we can build a copyable navigation aid for uncertain waters &ndash; a reference index, a catalog of findable landmarks. It has fallen naturally to the instance admins to administer justice &ndash; and yet we barely have the seeds of a set of best practices. We've done well crafting our Codes of Conduct to define the responsibilities of our users &ndash; but recent events have shown that we need Codes of Justice, to define (and limit) the responsibilities of our admins. Power must be accountable, and must be earned through its use in the service of the disempowered<ref name=banazi /> or else it is illegitimate. A Code of Justice needs to be able to answer certain questions: * As a user, how can I seek redress for harm done to me? * As an admin &mdash; ** under what circumstances am I enabled to act? ** under what circumstances do I have some moral obligation to act? ** what are the limits of the actions I may take? There are many different reasonable answers to these questions; I'm going to try to set out some for me to follow as admin of toot.cat. ==Footnotes== <references> <ref name=sydney>Apparently I now have a Sydney head-squirrel because I'm hearing strenuous objections to the idea that we could ever rely on any such thing, especially not now, and she's really quite skeptical that such a thing really exists in the first place, so the idea of depending on it for our safety is really kind of hecking scary. I'm... not ignoring her, but deferring that discussion for a later time; my statement was speculative and I agree we're not ready to go there yet.</ref> <ref name=banazi>This is essentially why we penalize instances that enable right-wing propaganda: they are failing in their service to the disempowered. They fail to protect the weak from the strength of induced collective hostility.</ref> </references> 02cf3cb731eec68ab9ef86c7c490ae69c20743db 43 42 2018-04-05T19:08:43Z Woozle 1 Woozle moved page [[Pub/user/woozle/2018/04/03/justice in the fediverse]] to [[Pub/user/woozle/2018/04/05/justice in the fediverse]] without leaving a redirect: make it today's date wikitext text/x-wiki <big> : ''I strive to evaluate first in terms of potential harm.'' : ''I strive to keep my emotions on hold until I have all the facts.'' </big> I'm working towards a redesigned process of justice. What I've come up with isn't as radically revisioned as what I'd like to do in the long run, but I don't have the tools for that yet. Traditional justice systems are usually based on hierarchies &ndash; something that has harmed many of us and which I believe most of us want to move away from. Justice should empower us all equally. Ideally, a system of justice would rely more on rallying our common sense of empathy<ref name=sydney /> to create the authority necessary to exercise power against malicious acts. To do that, we need tools that let us nurture and empower empathy, and disempower selfishness. We're not there yet. What we do have now is: * a fediverse, with a very simple and fairly short hierarchy: instance admins on the upper layer and regular users on the lower, with relatively minor and variable differences in power on each level, and * this wiki, in which I hope we can build a copyable navigation aid for uncertain waters &ndash; a reference index, a catalog of findable landmarks. It has fallen naturally to the instance admins to administer justice &ndash; and yet we barely have the seeds of a set of best practices. We've done well crafting our Codes of Conduct to define the responsibilities of our users &ndash; but recent events have shown that we need Codes of Justice, to define (and limit) the responsibilities of our admins. Power must be accountable, and must be earned through its use in the service of the disempowered<ref name=banazi /> or else it is illegitimate. A Code of Justice needs to be able to answer certain questions: * As a user, how can I seek redress for harm done to me? * As an admin &mdash; ** under what circumstances am I enabled to act? ** under what circumstances do I have some moral obligation to act? ** what are the limits of the actions I may take? There are many different reasonable answers to these questions; I'm going to try to set out some for me to follow as admin of toot.cat. ==Footnotes== <references> <ref name=sydney>Apparently I now have a Sydney head-squirrel because I'm hearing strenuous objections to the idea that we could ever rely on any such thing, especially not now, and she's really quite skeptical that such a thing really exists in the first place, so the idea of depending on it for our safety is really kind of hecking scary. I'm... not ignoring her, but deferring that discussion for a later time; my statement was speculative and I agree we're not ready to go there yet.</ref> <ref name=banazi>This is essentially why we penalize instances that enable right-wing propaganda: they are failing in their service to the disempowered. They fail to protect the weak from the strength of induced collective hostility.</ref> </references> 02cf3cb731eec68ab9ef86c7c490ae69c20743db 46 43 2018-04-07T12:57:00Z Woozle 1 formatting for principles-block wikitext text/x-wiki {{box/principles| : I strive to evaluate first in terms of potential harm. : I strive not to decide until I have all the facts. }} I'm working towards a redesigned process of justice. What I've come up with isn't as radically revisioned as what I'd like to do in the long run, but I don't have the tools for that yet. Traditional justice systems are usually based on hierarchies &ndash; something that has harmed many of us and which I believe most of us want to move away from. Justice should empower us all equally. Ideally, a system of justice would rely more on rallying our common sense of empathy<ref name=sydney /> to create the authority necessary to exercise power against malicious acts. To do that, we need tools that let us nurture and empower empathy, and disempower selfishness. We're not there yet. What we do have now is: * a fediverse, with a very simple and fairly short hierarchy: instance admins on the upper layer and regular users on the lower, with relatively minor and variable differences in power on each level, and * this wiki, in which I hope we can build a copyable navigation aid for uncertain waters &ndash; a reference index, a catalog of findable landmarks. It has fallen naturally to the instance admins to administer justice &ndash; and yet we barely have the seeds of a set of best practices. We've done well crafting our Codes of Conduct to define the responsibilities of our users &ndash; but recent events have shown that we need Codes of Justice, to define (and limit) the responsibilities of our admins. Power must be accountable, and must be earned through its use in the service of the disempowered<ref name=banazi /> or else it is illegitimate. A Code of Justice needs to be able to answer certain questions: * As a user, how can I seek redress for harm done to me? * As an admin &mdash; ** under what circumstances am I enabled to act? ** under what circumstances do I have some moral obligation to act? ** what are the limits of the actions I may take? There are many different reasonable answers to these questions; I'm going to try to set out some for me to follow as admin of toot.cat. ==Footnotes== <references> <ref name=sydney>Apparently I now have a Sydney head-squirrel because I'm hearing strenuous objections to the idea that we could ever rely on any such thing, especially not now, and she's really quite skeptical that such a thing really exists in the first place, so the idea of depending on it for our safety is really kind of hecking scary. I'm... not ignoring her, but deferring that discussion for a later time; my statement was speculative and I agree we're not ready to go there yet.</ref> <ref name=banazi>This is essentially why we penalize instances that enable right-wing propaganda: they are failing in their service to the disempowered. They fail to protect the weak from the strength of induced collective hostility.</ref> </references> 11ccbe1756e47d9e535bd3675d618d74636006d3 0 16 44 26 2018-04-05T19:09:29Z Woozle 1 eine kleine blogpost wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} 9dcf2318192946eaf3db2059f26a54675b1358ea 49 44 2018-04-07T13:57:55Z Woozle 1 sketching a code wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} * {{ld/blog|2018-04-07|sketching a code}} a7f80ededb7c0944e3cb520bbfb76e1f9b3c765e 10 23 45 2018-04-07T12:53:35Z Woozle 1 Created page with "{| align=right border=1 |- | align=right style="font: italic bold 18pt/16pt Times, serif; color: #eee; background: #666;" | {{{1}}} |}" wikitext text/x-wiki {| align=right border=1 |- | align=right style="font: italic bold 18pt/16pt Times, serif; color: #eee; background: #666;" | {{{1}}} |} be5d6fca0b30a4c98f09852d7a13d11a9cf7e8bf 47 45 2018-04-07T12:59:25Z Woozle 1 a bit of padding wikitext text/x-wiki {| align=right border=1 cellpadding=10 |- | align=right style="font: italic bold 18pt/16pt Times, serif; color: #eee; background: #666;" | {{{1}}} |} d17534364416bc0ad85462632bf699a8fb21f404 0 24 48 2018-04-07T13:57:48Z Woozle 1 Created page with "{{box/principles| : Words have consequences. : All accusations should be taken seriously. : No accusation should be accepted as truth unless the evidence supports it. : Both a..." wikitext text/x-wiki {{box/principles| : Words have consequences. : All accusations should be taken seriously. : No accusation should be accepted as truth unless the evidence supports it. : Both accusers and accused may need some protection. : A lie often contains just enough truth to make it plausible. }} ==Public Intervention Process<ref name=pip />== Other instances may adopt this, modify it, or ignore it completely; I'm content to let the marketplace of kindness<ref name=note1 /> decide whether such a thing is necessary or not, and to let the process of considered discussion refine it as needed &ndash; but tentatively, here's the way I think it should work for toot.cat. '''If you have a grievance against another user'''<ref name=note2 /> and would like me (as sysop of this instance) to do something about it: # "@" me (@woozle@toot.cat) with a public<ref name=public /> toot stating the nature of the problem and that you are requesting an Intervention. #* The primary types of problem I expect to be addressing are: (a) someone has abused you, or (b) someone has falsely accused you of abuse &ndash; but others may emerge. # This means I have your permission to investigate the situation and publicly post my findings on Mew (this wiki). #* I will probably need to ask a lot of nosy questions, both to you and the other parties involved. Let me know if you anticipate any problems with this. #* These discussions should take place on Mastodon<ref name=mastodm /> so as to be part of the public record, though I can make exceptions if there's a good reason. # Once I have investigated sufficiently to satisfy ''my'' standards of evidence, I will post a preliminary determination for public feedback. # Anyone may state objections to this conclusion at any time, and I will either answer them or reconsider my conclusion, possibly re-opening the investigation. # Anyone may choose to go on record as supporting or opposing the conclusion. I will make these part of the public record to the best of my ability. #* Please note that opposition is not the same as stating an objection. I won't reconsider just because you oppose; you need to make an argument for why it is wrong. Please note that this is a good-faith process &ndash; i.e. one that depends on all participants being honest about their beliefs and intentions &ndash; and I will deal firmly with anyone I find to be acting otherwise. I have over a decade of experience spotting manipulation and evasion in online arguments. ==Footnotes== <references> <ref name=note1>This is a reference to the semi-capitalistic "marketplace of ideas" concept, with an ironic twist since capitalists don't seem to place much (if any) value on kindness (so their marketplaces tend to squash it out of existence) and since most Mastodonians are staunchly anti-marketist. That said, the idea of having numerous instances among which users may freely choose to invest various amounts of their time and energy actually ''is'' a kind of marketplace that's totally compatible with anarcho-capitalism &ndash; except I think we'd all tend to agree that basically having one person who gets to decide pretty much everything about how the system works is kind of iffy.</ref> <ref name=note2>This applies whether or not either user is on toot.cat, though obviously my actions will be more effective if one or the other is.</ref> <ref name=public>You could also approach me privately (DM or whatever) to discuss it before stating it publicly, or you might need me to try to keep your name out of the public process. I'm willing to consider intervening less publicly, but I suspect it will severely limit any good I might be able to do; if this emerges as a frequent need, I'll probably need to write up a separate process for dealing with it.</ref> <ref name=pip>It seems entirely appropriate that this abbreviates to PIP, which is also the name of our very messed-up cat ([https://toot.cat/@Pip Mastodon], [https://wiki.hypertwins.org/Pip HypertWiki]), since it is only invoked when a situation has become very messed-up. It is my hope that this process will soon become informally known as "requesting a Pip".</ref> <ref name=mastodm>Tentatively, this should be public but "unlisted" or "followers only". I may need to set up a dedicated investigation account so people can decide whether they want the investigation in their streams or not.</ref> </references> 1370855f907cd19de4fed13fbf87772cd350b54f 0 173 543 2018-04-07T21:57:34Z Woozle 1 Created page with "Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll...." wikitext text/x-wiki Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev</code> * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code>: ** <code>su - mastodon</code> WORKING HERE. bc7d960d913473fd3e72878813c4986fd3ae6577 544 543 2018-04-08T00:52:53Z Woozle 1 wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. 2d658a0409c13e9d2ce3e74f24ee8f894c8e2559 545 544 2018-04-09T11:57:20Z Woozle 1 saving latest work wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. (resuming on 2018-04-09) Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> ''still working on this; saving work so far'' 4d5a3a4e6143f9eefd4717343cc66235c216855e 546 545 2018-04-09T12:09:41Z Woozle 1 latest obstacle wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. (resuming on 2018-04-09) Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </code> b7bb35a54b63c6ddd5384c2bdf0e9bae8874f3fa 547 546 2018-04-09T13:51:26Z Woozle 1 latest sticking poin t wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. (resuming on 2018-04-09) Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. 539126deae2f5cb7e67944b01006b75f7f6572ac 548 547 2018-04-09T14:11:32Z Woozle 1 wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. (resuming on 2018-04-09) Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. <code>bundle --help</code> gives man-style help which lists all the bundle commands; <code>bundle install --help</code> lists options specific to <code>bundle install</code>, and none of the <code>--with-idn-*</code> options appear to be among either of them. * How about: <code>gem install idn-ruby</code>... nope, same error message... * How about <code>gem install idn-ruby --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code>... ** nope: <code>invalid option: --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> 3b0dccb051ae9d0aef1891d097fe529109c64de7 549 548 2018-04-09T23:41:17Z Woozle 1 wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. ===part 2=== Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. <code>bundle --help</code> gives man-style help which lists all the bundle commands; <code>bundle install --help</code> lists options specific to <code>bundle install</code>, and none of the <code>--with-idn-*</code> options appear to be among either of them. * How about: <code>gem install idn-ruby</code>... nope, same error message... * How about <code>gem install idn-ruby --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code>... ** nope: <code>invalid option: --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ===part 3=== Some [https://cybre.space/@benhamill/99831608699607241 research] by Ben Hamill suggested this: <code>gem install --remote idn</code> The resulting error message pointed me at a log file, which seemed to be saying that the problem was coming from [[gcc]]. Since this means there was compiling involved, I thought maybe I should install the header file for idn as well (as root): <code>apt install libghc-gnuidn-dev</code>. Followed by... * <code>su - mastodon</code> * <code>gem install --remote idn</code> Output: <pre>Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-23716-rrnxuy.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Oops, maybe I was supposed to be in <code>~/live</code>? Logging in again as root... * <code>su - mastodon</code> * <code>cd live</code> * <code>gem install --remote idn</code> Output:<pre> Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-24783-1trgchl.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Looks pretty much the same. 8b4053d4ea2395813bf9544f470b39a6c18f132a 550 549 2018-04-10T10:42:01Z Woozle 1 wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. ===part 2=== Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. <code>bundle --help</code> gives man-style help which lists all the bundle commands; <code>bundle install --help</code> lists options specific to <code>bundle install</code>, and none of the <code>--with-idn-*</code> options appear to be among either of them. * How about: <code>gem install idn-ruby</code>... nope, same error message... * How about <code>gem install idn-ruby --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code>... ** nope: <code>invalid option: --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ===part 3=== Some [https://cybre.space/@benhamill/99831608699607241 research] by Ben Hamill suggested this: <code>gem install --remote idn</code> The resulting error message pointed me at a log file, which seemed to be saying that the problem was coming from [[gcc]]. Since this means there was compiling involved, I thought maybe I should install the header file for idn as well (as root): <code>apt install libghc-gnuidn-dev</code>. Followed by... * <code>su - mastodon</code> * <code>gem install --remote idn</code> Output: <pre>Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-23716-rrnxuy.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Oops, maybe I was supposed to be in <code>~/live</code>? Logging in again as root... * <code>su - mastodon</code> * <code>cd live</code> * <code>gem install --remote idn</code> Output:<pre> Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-24783-1trgchl.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Looks pretty much the same. All I can think is that this is some kind of version conflict caused by me originally installing the wrong version of Ruby (because that's the version the instructions specified), so let's scrap this build and start over. 55e2d440b7847e48a8eeefbfa9bdb464852b51e2 0 172 539 2018-04-11T11:36:20Z Woozle 1 Created page with "Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/P..." wikitext text/x-wiki Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] from the start this time, but using Ruby 2.5.0 instead of 2.4.1. Skipping the server-creation and DNS bits because I do those without thinking. (Also, can't point the real domain here until later.) These instructions assume you're running as root, which works for me. * <code>mkdir setup</code> (/root/setup) * <code>cd setup</code> - because I like to keep setup clutter in a separate folder * <code>wget https://deb.nodesource.com/setup_6.x</code> * <code>bash setup_6.x</code> * <code>apt -y install curl</code> - was already the latest version * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ''had to stop here'' 12e9da0ca7c257dd53d3c68c2b9ee89dfed04dc2 540 539 2018-04-11T14:48:28Z Woozle 1 wikitext text/x-wiki Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] from the start this time, but using Ruby 2.5.0 instead of 2.4.1. Skipping the server-creation and DNS bits because I do those without thinking. (Also, can't point the real domain here until later.) These instructions assume you're running as root, which works for me. * <code>mkdir setup</code> (/root/setup) * <code>cd setup</code> - because I like to keep setup clutter in a separate folder * <code>wget https://deb.nodesource.com/setup_6.x</code> * <code>bash setup_6.x</code> * <code>apt -y install curl</code> - was already the latest version * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> At this point (morning of 4/11), I turned the problem over to Lottie... * [https://gist.github.com/foxsan48/dad39f49777794d60594905e85e8fc45 Gist] * [https://toot.cat/@woozle/99841228289384064 toot to StaticSafe] 8c0b8850c5b457954eda4f4bcce68ab735f32e80 10 25 51 2018-04-20T12:02:37Z Woozle 1 pirated from ASP wiki wikitext text/x-wiki <includeonly>[[category:seeds]]</includeonly> {| style="background: #ffffee; border: 1px solid #88bb00;" align=center |- | <div class="boilerplate" id="stub">&hearts; ''This article needs more nurturing to help it reach its full potential''. {{{1|}}} </div> |} 5ca40b2e2cf171ddb7eddaeded693cabdf3ec94f 0 26 52 2018-04-20T12:03:00Z Woozle 1 Created page with "[[category:Mastodon instances]] {{seed}} ==Links== * https://dev.glitch.social/@cassolotl/99890887832152105 - screencap showing Switter reaching 50k+ users" wikitext text/x-wiki [[category:Mastodon instances]] {{seed}} ==Links== * https://dev.glitch.social/@cassolotl/99890887832152105 - screencap showing Switter reaching 50k+ users 35862447ce03f5a95920465208736c51ced5a178 8 2 54 3 2018-04-27T10:02:11Z Woozle 1 contribution link wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** Help:Contribute|Contribute ** Help:Main|help * SEARCH * TOOLBOX * LANGUAGES 9b47145b8e7c40e49a6ee2eff7e48c2075d74401 12 27 55 2018-04-27T10:21:49Z Woozle 1 first draft wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''': ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running ==Resources== We need to maintain a wish-list... 54b76037d82754043419c3dd01b841c987413b8b 56 55 2018-04-27T10:35:57Z Woozle 1 individual Lp links wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Charlotte''': ** [https://liberapay.com/LottieVixen/ LiberaPay] * '''Woozle''': ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running ==Resources== We need to maintain a wish-list... fb009ddbca434e4c1b75fefb33884e0dd737c242 58 56 2018-04-28T11:49:22Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Charlotte''': ** [https://liberapay.com/LottieVixen/ LiberaPay] * '''Woozle''': ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running You can also mail checks to: : Nick Staddon : 122 Pinecrest Rd. : Durham, NC 27705 ==Resources== We need to maintain a wish-list... 00b4a77732aaa0ea9109da885f24fe619138c435 68 58 2018-05-02T01:00:21Z Woozle 1 found 2 more for Lottie wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Charlotte''': ** [https://liberapay.com/LottieVixen/ LiberaPay] ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] * '''Woozle''': ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running You can also mail checks to: : Nick Staddon : 122 Pinecrest Rd. : Durham, NC 27705 ==Resources== We need to maintain a wish-list... e81ed45e7345c80d89aabbb6672a003b7b9110f2 12 3 59 4 2018-04-29T21:25:19Z Woozle 1 wikitext text/x-wiki More help stuff needs to go here, but for now... ==Mastodon== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Mew== * [[Help:Admin]]: wiki administration help d5959dbcf5d379add5c197b5e0c1e41497b7f027 12 4 60 5 2018-04-29T23:21:17Z Woozle 1 wikitext text/x-wiki This page is help information for site administrators. * [[mediawiki:sidebar]]: contents of the navigation column on the left * [[MediaWiki:Common.css]]: CSS to apply to all pages ==Notes== * '''2018-04-29''' [https://elekk.xyz/@noelle/99944487524259981 When witches.town goes down in the next few days...]: a thing for improving Mastodon performance afterwards c08d8f1da1677b47300f714a9e2977d9d374bc51 6 28 64 2018-04-30T11:28:24Z Woozle 1 * '''what''': results of [https://docs.google.com/spreadsheets/d/1M2ig66m9bLSTOtXOj2rOWNkobQ1slTkgiyztlzaWu7Y/edit?usp=sharing survey] about where witches.town users are moving to * '''retrieved''' from [https://dev.glitch.social/@cassolotl/99947935739... wikitext text/x-wiki * '''what''': results of [https://docs.google.com/spreadsheets/d/1M2ig66m9bLSTOtXOj2rOWNkobQ1slTkgiyztlzaWu7Y/edit?usp=sharing survey] about where witches.town users are moving to * '''retrieved''' from [https://dev.glitch.social/@cassolotl/99947935739267460 dev.glitch.social] on 2018-04-30 cc8dcc19eeeebe306d4b73773fe359fc6c42d7af 65 64 2018-04-30T11:29:04Z Woozle 1 Woozle uploaded a new version of [[File:B03116fbd6f7793f.png]] wikitext text/x-wiki * '''what''': results of [https://docs.google.com/spreadsheets/d/1M2ig66m9bLSTOtXOj2rOWNkobQ1slTkgiyztlzaWu7Y/edit?usp=sharing survey] about where witches.town users are moving to * '''retrieved''' from [https://dev.glitch.social/@cassolotl/99947935739267460 dev.glitch.social] on 2018-04-30 cc8dcc19eeeebe306d4b73773fe359fc6c42d7af 0 171 536 2018-05-03T11:46:05Z Woozle 1 Created page with "Reference links: * [https://rm.vbz.net/projects/toot-cat/issues issue on Redmine] * [https://github.com/tootsuite/mastodon/issues/7323 help request on tootsuite@GitHub] <code..." wikitext text/x-wiki Reference links: * [https://rm.vbz.net/projects/toot-cat/issues issue on Redmine] * [https://github.com/tootsuite/mastodon/issues/7323 help request on tootsuite@GitHub] <code>journalctl -u mastodon-sidekiq | grep smtp</code> yields this: <pre> May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' May 03 11:15:21 tootcat2 bundle[5368]: 2018-05-03T11:15:21.238Z 5368 TID-orv43zy6g WARN: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' </pre> ...with several prior instances of very similar sequences. 248f2342a55a7c1b93daca921b2b90de2fd3c4b4 0 171 537 536 2018-05-03T23:44:18Z Woozle 1 solution wikitext text/x-wiki Reference links: * [https://rm.vbz.net/projects/toot-cat/issues issue on Redmine] * [https://github.com/tootsuite/mastodon/issues/7323 help request on tootsuite@GitHub] ==Solution== # You have to restart (or reload?) the SideKiq job, possibly in addition to the web job. # Installing Postfix and using these settings works well: <pre> SMTP_SERVER=localhost SMTP_PORT=25 SMTP_AUTH_METHOD=none SMTP_OPENSSL_VERIFY_MODE=none </pre> ==Notes== <code>journalctl -u mastodon-sidekiq | grep smtp</code> yields this: <pre> May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' May 03 11:15:21 tootcat2 bundle[5368]: 2018-05-03T11:15:21.238Z 5368 TID-orv43zy6g WARN: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' </pre> ...with several prior instances of very similar sequences. 9bf9145fef6896b83be5faa2106b7c132f007334 0 1 69 67 2018-05-03T23:50:09Z Woozle 1 old news from front page; email issue solved wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 39333ac4113bd36fad880bc6fd93bc415339d2f0 71 69 2018-05-20T17:17:30Z Woozle 1 5/20 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-20''' Rebooting the server (long overdue). Watch this space for issues. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> bac24aab12412b932c71207e25659707bbf02bbf 72 71 2018-05-20T17:25:13Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot has resulted in all message windows being depopulated. I have retreated to the TootCave to focus on the problem. *** Feel free to message me at [https://dev.glitch.social/@woozle @woozle@dev.glitch.social] in the meantime. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> c3a4bcacf0b1f79bde98697127f0a546e93e36e0 73 72 2018-05-20T18:04:31Z Woozle 1 issue resolved wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the TootCave to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 98be1e3ed453be602c4af1dc50e053cb3b487675 81 73 2018-05-20T19:54:45Z Woozle 1 link to TootCave page wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the Mastoverse, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> c394368ff135148311517e589775ada0bfd10690 91 81 2018-05-23T20:14:32Z Woozle 1 Mastoverse page link; spambots wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> afa9b7472104a783ba29495617ac7bf9ad6735db 92 91 2018-05-30T23:48:13Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-30''' The SSL certificate seems to have failed to renew on the new server. Investigating. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 651607da330ef47dabfc0f238b4acc1979600ae2 93 92 2018-05-31T11:38:15Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> aafc4c1e5b71f8483947847cc719171f2a015df3 94 93 2018-06-02T12:52:47Z Woozle 1 /* Mastodon News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 9fb188e5b21ac74f4cb16a4c020b50caa33c36d9 99 94 2018-06-03T12:58:45Z Woozle 1 forkdrama wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-06-02''' A lot of anger and resentment brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 7a78acba9b2f9f084531a7ba94f4215d5df8599a 100 99 2018-06-03T13:00:03Z Woozle 1 forkdrama was supposed to be in Mastodon News, not Site News wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> b4faee60e09ce2dbcb47d68beb098d215df5cf7d 105 100 2018-06-05T13:57:55Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. In a good faith effort to satisfy the [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf .cat TLD requirements], we will also be collecting information about {{l/pub|Catalonia}} as it comes our way and doing what we can to make the domain useful for Catalonian/Catalan interests. * [[Mew:About]]: what this wiki is about ==Site News== * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 36df256ef41f11a75882ca1ec4d9613b99c0b914 108 105 2018-06-05T14:53:54Z Woozle 1 talk about .cat on separate page wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ==Site News== * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 89dfe5f987935425f0c042bda143743983bb45b5 110 108 2018-06-11T00:28:02Z Woozle 1 my public pages wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD * {{l/pub|user/woozle}}: Woozle's public pages ==Site News== * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 3b16ecd3d5a3b0db5c2c795c35bb8d71f6088e7e 0 29 70 2018-05-05T00:35:25Z Woozle 1 Created page with "==Links== ===Video=== * [https://exode.me/videos/watch/a4d6ebb3-8f61-48c7-88fd-3246de039725 History of Catalonia]" wikitext text/x-wiki ==Links== ===Video=== * [https://exode.me/videos/watch/a4d6ebb3-8f61-48c7-88fd-3246de039725 History of Catalonia] adf8dabe6cf291bc099dca79aacba94d8cfa474c 104 70 2018-06-05T13:53:29Z Woozle 1 wikitext text/x-wiki ==Links== ===Events=== * '''2018-06-13''' [https://www.cooperativestreball.coop/esdeveniments/2018/06/05/benvingudes-noves-cooperatives Benvingudes noves cooperatives] (auto-translated) "A session for the recently federated cooperatives to approach the Federation of Cooperatives of Work of Catalonia and know in detail who we are, what we do and how we organize." ===Video=== * [https://exode.me/videos/watch/a4d6ebb3-8f61-48c7-88fd-3246de039725 History of Catalonia] a5dee6ca65d4fa3bd4c9bb4dd94d8aa626362a58 0 170 534 2018-05-20T17:52:45Z Woozle 1 issue documentation wikitext text/x-wiki * '''symptom''': Main page came up, but with no toots. Some other pages would not respond at all. * '''cause''': ** [[Nginx]] wasn't starting, and the status returned by <code>systemctl status nginx.service</code> included the message <code>bind() to [::]:443 failed (98: Address already in use)</code>. ** This was in turn because of a small problem in <code>/etc/nginx/sites-available/tootcat2.hypertwins.net.conf</code>. The lines of interest are:<pre> server { listen 443 ssl; listen [::]:443 ssl ipv6only=on; </pre> The last line ''was'' set to <code>ipv6only=off</code>. What that apparently means is that this line will try to listen on [[IPv4]] as well &ndash; but the previous line already has nginx trying to listen on IPv4, so nginx fails when it tries to listen again on the same port. Specifying <code>ipv6only=on</code> tells it "this line means you're supposed to ''only'' listen on [[IPv6]], so don't try anything else here.", resulting in nginx listening on both IPv4 and IPv6, which is what we want. I don't know why it was even working before; maybe the behavior of nginx changed between versions. 6369e6c70ba349fee315f74daa07966e793e091c 6 30 74 2018-05-20T19:35:51Z Woozle 1 * '''what''': The {{l/pub|TootCave}} * '''when''': 2018-05-20 wikitext text/x-wiki * '''what''': The {{l/pub|TootCave}} * '''when''': 2018-05-20 fbd8c3cb8c4ef718963a80e38201f09ca11cc38f 6 32 76 2018-05-20T19:42:13Z Woozle 1 * '''what''': The {{l/pub|TootCave}} * '''when''': 2018-05-20 wikitext text/x-wiki * '''what''': The {{l/pub|TootCave}} * '''when''': 2018-05-20 fbd8c3cb8c4ef718963a80e38201f09ca11cc38f 6 33 77 2018-05-20T19:43:32Z Woozle 1 * '''what''': The {{l/pub|TootCave}} * '''when''': 2018-05-20 wikitext text/x-wiki * '''what''': The {{l/pub|TootCave}} * '''when''': 2018-05-20 fbd8c3cb8c4ef718963a80e38201f09ca11cc38f 0 34 78 2018-05-20T19:46:39Z Woozle 1 does this render differently after saving? wikitext text/x-wiki <center> =The TootCave= ''aka [https://toot.cat/web/accounts/1132 @Harena]'s basement'' This is where {{lpub/user|woozle}} retreats to brood over the state of humanity and also to fix server stuff and sometimes code. [[File:IMG 20180520 140507818.jpg|500px]] [[File:IMG 20180520 140536048.jpg|frame|500px|The tools of world domination]] [[File:IMG 20180520 140549054.jpg|800px|The Seat of Power -- from which Woozle hears all, sees all, knows all]] </center> 08809936205aadb9952ec9aedec29278b81c31a5 79 78 2018-05-20T19:51:50Z Woozle 1 reaching point of diminishing returns; I guess this will do wikitext text/x-wiki ='''The TootCave'''= ''aka [https://toot.cat/web/accounts/1132 @Harena]'s basement'' This is where {{lpub/user|woozle}} retreats to brood over the state of humanity and also to fix server stuff and sometimes code. [[File:IMG 20180520 140507818.jpg|thumb|left|500px]] [[File:IMG 20180520 140536048.jpg|thumb|right|500px|The tools of world domination]] [[File:IMG 20180520 140549054.jpg|thumb|left|800px|The Seat of Power -- from which Woozle hears all, sees all, knows all]] 73a52192c2616a81b8ae0ef85fdcbf9f36f7b0e3 80 79 2018-05-20T19:54:30Z Woozle 1 caption for pic #1 wikitext text/x-wiki ='''The TootCave'''= ''aka [https://toot.cat/web/accounts/1132 @Harena]'s basement'' This is where {{lpub/user|woozle}} retreats to brood over the state of humanity and also to fix server stuff and sometimes code. [[File:IMG 20180520 140507818.jpg|thumb|left|500px|The wall bears strange inscriptions from another epoch.<br>Also, old trampoline parts.]] [[File:IMG 20180520 140536048.jpg|thumb|right|500px|The tools of world domination]] [[File:IMG 20180520 140549054.jpg|thumb|left|800px|The Seat of Power -- from which Woozle hears all, sees all, knows all]] 9e61b675fbf9578dbcdcc58f7d059b2fb7fb86fb 0 16 82 49 2018-05-21T00:56:53Z Woozle 1 TootCave wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. Also, have some photos of The {{l/pub|TootCave}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} * {{ld/blog|2018-04-07|sketching a code}} 2f23173b59d90c2395a31664b8979216a0866e70 0 26 83 52 2018-05-23T19:45:32Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] {{seed}} ==Links== * https://dev.glitch.social/@cassolotl/99890887832152105 - screencap showing Switter reaching 50k+ users a462ce58d9a4d47e9f05c02caa13bb2d83405b05 0 18 84 66 2018-05-23T19:46:08Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) is still, as of this writing, a Mastodon instance. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99757948365320502 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] b225e3d917e165688057f4007a05bdfc1ce49acf 0 35 85 2018-05-23T19:46:18Z Woozle 1 Created page with "[[category:instances]] ==Notes== * https://mastodon.starrevolution.org/@Laurelai/100080256575111626" wikitext text/x-wiki [[category:instances]] ==Notes== * https://mastodon.starrevolution.org/@Laurelai/100080256575111626 bcc55b8c077c78120c4340354ca3d647229e0ffe 90 85 2018-05-23T20:11:30Z Woozle 1 wikitext text/x-wiki [[category:instances]] ==Notes== * https://mastodon.starrevolution.org/@Laurelai/100080256575111626 ** https://mastodon.starrevolution.org/@Laurelai/100080413877659466 8210ff9cc2306965f9d5c6e4f8e8d21c5be5b856 14 36 86 2018-05-23T19:46:48Z Woozle 1 Created page with "instances on the Mastodon fediverse" wikitext text/x-wiki instances on the Mastodon fediverse cc559d5b53aee4627900da92dc7037d8e634c64e 10 37 87 2018-05-23T20:10:33Z Woozle 1 Created page with ":category:{{{1}}}|{{{1}}}" wikitext text/x-wiki [[:category:{{{1}}}|{{{1}}}] c5f0e23337680c87c54aba82cb76f5bf14646f0a 88 87 2018-05-23T20:10:50Z Woozle 1 wikitext text/x-wiki [[:category:{{{1}}}|{{{1}}}]] 17c6dcc469472a3bc55ff465fc3510ff5968e85e 0 38 89 2018-05-23T20:11:18Z Woozle 1 Created page with "The '''Mastoverse''' is the Mastodon-compatible fediverse, i.e. all the federated Mastodon instances as well as instances of other software that federates with Mastodon (inclu..." wikitext text/x-wiki The '''Mastoverse''' is the Mastodon-compatible fediverse, i.e. all the federated Mastodon instances as well as instances of other software that federates with Mastodon (including GNUSocial and Pleroma). ==Pages== * {{lc|instances}}: list of instances we have pages about 23461b346c89b81b0a7d4edcc10a96338d0b1e13 0 169 526 2018-05-31T01:38:13Z Woozle 1 saving work wikitext text/x-wiki It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ==Phase 2== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ==Phase 3== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> 39c9527491fe2704fd3e2382f05aa218c2ff2708 527 526 2018-05-31T10:36:55Z Woozle 1 Phase 5: from Discord wikitext text/x-wiki It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ==Phase 2== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ==Phase 3== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ==Phase 4== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ==Phase 5== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> eb879e040db84c887c5a512b439f6c16f730929c 528 527 2018-05-31T11:18:41Z Woozle 1 wrap-up wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS). * A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. (Addressing this first.) ==Narration / Notes== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ==Phase 2== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ==Phase 3== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ==Phase 4== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ==Phase 5== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 18377ea90ad8487e6f224326514ddbda1ff2785b 529 528 2018-05-31T11:36:19Z Woozle 1 wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS). * A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.) ==Narration / Notes== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ==Phase 2== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ==Phase 3== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ==Phase 4== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ==Phase 5== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 4dcc5b824869430380d633c98d91172a9e5d16c4 530 529 2018-05-31T13:47:04Z Woozle 1 files; tidying wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS). * <s>A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.)</s> ===Relevant Files=== * <code>/etc/letsencrypt/renewal/tootcat.conf</code> - Let's Encrypt configuration * <code>/etc/nginx/sites-available/tootcat.conf</code> - Nginx configuration * <code>/etc/cron.daily/letsencrypt-renew</code> - the [[cron]] job to check/renew the cert ==Narration / Notes== ===Phase 1=== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ===Phase 2=== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ===Phase 3=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 4=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 5=== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 7dd2dad0d910578eb6801f485b1a9c2de223a6ca 531 530 2018-05-31T14:32:51Z Woozle 1 /* Relevant Files */ another one wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS). * <s>A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.)</s> ===Relevant Files=== * <code>/etc/cron.daily/letsencrypt-renew</code> - the [[cron]] job to check/renew the cert * <code>/etc/letsencrypt/renewal/tootcat.conf</code> - Let's Encrypt configuration * <code>/etc/nginx/sites-available/tootcat.conf</code> - Nginx configuration * <code>/var/log/nginx/access.log</code> - Nginx access log (showed 404 when accessing via IPv6) ==Narration / Notes== ===Phase 1=== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ===Phase 2=== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ===Phase 3=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 4=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 5=== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 81df29a910f2e8bdf44f49882a3daf6b3e532500 0 172 541 540 2018-05-31T11:03:49Z Woozle 1 more follow-up wikitext text/x-wiki Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] from the start this time, but using Ruby 2.5.0 instead of 2.4.1. Skipping the server-creation and DNS bits because I do those without thinking. (Also, can't point the real domain here until later.) These instructions assume you're running as root, which works for me. * <code>mkdir setup</code> (/root/setup) * <code>cd setup</code> - because I like to keep setup clutter in a separate folder * <code>wget https://deb.nodesource.com/setup_6.x</code> * <code>bash setup_6.x</code> * <code>apt -y install curl</code> - was already the latest version * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> At this point (morning of 4/11), I turned the problem over to Lottie... * [https://gist.github.com/foxsan48/dad39f49777794d60594905e85e8fc45 Gist] * [https://toot.cat/@woozle/99841228289384064 toot to StaticSafe] * There are also some notes in [https://rm.vbz.net/projects/toot-cat-sysops/wiki toot.cat private on Redmine] that could be made public 41097f6906afd91958f13e29e2014b862b160851 0 39 95 2018-06-02T13:07:55Z Woozle 1 Created page with "==Notes== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about]" wikitext text/x-wiki ==Notes== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about] a5b47c852cadd01599a01f56add4a612abe3dfd5 96 95 2018-06-02T13:08:27Z Woozle 1 wikitext text/x-wiki [[category:instances]] [[category:Mastodon]] ==Notes== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about] 099689ad99da6025b9daee856ea47accf82f0bfb 97 96 2018-06-02T13:14:38Z Woozle 1 wikitext text/x-wiki [[category:instances]] [[category:Mastodon]] ==Contact== Sysop seems to be Valentin Ouvrard: * [https://twitter.com/Valentin_NC Twitter] * [https://www.patreon.com/ValentinOuvrard Patreon] ** [https://twitter.com/Woozalia/status/1002900363647832065 Woozle asks what's up] ==Archives== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about] e2570f08d450f72acf317d088ecd54b021e08eec 103 97 2018-06-05T13:20:20Z Woozle 1 update wikitext text/x-wiki [[category:instances]] [[category:Mastodon]] ==Contact== Sysop seems to be Valentin Ouvrard: * [https://twitter.com/Valentin_NC Twitter] * [https://www.patreon.com/ValentinOuvrard Patreon] ** [https://twitter.com/Woozalia/status/1002900363647832065 Woozle asks what's up] ==News== * '''2018-06-04''' Tweet: [https://mobile.twitter.com/Valentin_NC/status/1003528732223475717 "Yeah, I'm currently in migration to Japan datacenter, It take a while due of the instance size... We will back soon :)"] * '''2018-06-02''' [https://toot.cat/@RefurioAnachro/100134355499771070 A mastodon.cloud refugee reports] that the instance has been down for over a week. ==Archives== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about] 62c30a129126369f21e6930e658b7eb643739d8f 0 40 98 2018-06-03T12:58:06Z Woozle 1 Created page with "==Notes== * '''2018-06-03''' [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. * [https://github.com/..." wikitext text/x-wiki ==Notes== * '''2018-06-03''' [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. * [https://github.com/tootsuite/mastodon/issues/7702 GitHub issue #7702: Admin Option to Disable Trending Feature] ** https://mastodon.social/@Gargron/100140965702165118 e92c1e3ea0d18dcf4625e50970f584194c2f770f 101 98 2018-06-03T17:59:04Z Woozle 1 Maloki's links wikitext text/x-wiki ==Notes== * '''2018.06.03''' ** [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. ** [https://elekk.xyz/@maloki/100141486585398752 What is ForkOff/Together?] * '''2018.06.01-03''' [https://github.com/tootsuite/mastodon/issues/7702 GitHub issue #7702: Admin Option to Disable Trending Feature] ** '''2018.06.03''' [https://mastodon.social/@Gargron/100140965702165118 I've locked the discussion so nobody can comment on it anymore but...] cb5dbf41203d5c151c928adb07c503954a4775ee 102 101 2018-06-04T14:07:05Z Woozle 1 wikitext text/x-wiki ==Notes== * '''2018.06.04''' [https://social.coop/@kittybecca/100145873112206294 yesterday apparently the hashtag DropTheT trended on twitter...]: one reason why trending tags is a problematic feature * '''2018.06.03''' ** [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. ** [https://elekk.xyz/@maloki/100141486585398752 What is ForkOff/Together?] * '''2018.06.01-03''' [https://github.com/tootsuite/mastodon/issues/7702 GitHub issue #7702: Admin Option to Disable Trending Feature] ** '''2018.06.03''' [https://mastodon.social/@Gargron/100140965702165118 I've locked the discussion so nobody can comment on it anymore but...] d5b584d1e2529e1ea424c9f21514aa1d41d435a4 14 41 106 2018-06-05T14:52:42Z Woozle 1 description wikitext text/x-wiki pages about {{l/pub|Mastodon}} 82f85a45e6739d5e687d4a6f3a289600cfa76e0f 0 42 107 2018-06-05T14:53:34Z Woozle 1 Created page with "The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satis..." wikitext text/x-wiki The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about {{l/pub|Catalonia}} as it comes our way. * We are interested in making space for content related to Catalonia and/or Catalan. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} 15d06a40aad2674ac72de7b69d62080967c1e69e 109 107 2018-06-05T14:56:06Z Woozle 1 wikitext text/x-wiki The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about {{l/pub|Catalonia}} as it comes our way. * We are interested in making space for content related to Catalonia and/or Catalan. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Mastodon user Sam Toland [https://social.coop/@samtoland/100152739177441119 notes] that the .cat admins used to be much stricter, but have now loosened enforcement a bit. ecb6ca484ac87e9f74b90960611bbbeb8740e62c 0 1 111 110 2018-06-13T01:02:55Z Woozle 1 /* Site News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD * {{l/pub|user/woozle}}: Woozle's public pages ==Site News== * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> eaf1d8c04819f9a779be92ddf182ff867378ba00 113 111 2018-06-26T18:16:06Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of trolls, ideologues, and jerks ==Site News== * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> de090de250952bfa5228804d626f1bf983984f4d 121 113 2018-06-29T21:26:23Z Woozle 1 wasn't very obvious, was it wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of trolls, ideologues, and jerks ==Site News== * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> ad116930330552c9f4e00a6db68fbff375dc7878 122 121 2018-06-29T21:29:46Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> a6932c3f6d0669d675ee327b8e484c57d7892224 130 122 2018-06-30T23:34:51Z Woozle 1 /* Public Pages */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks * {{l/pub|ForkTogether}}: a project to create a more maintainable fediverse ==Site News== * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> b320e49adbf23c5c6000adddac9b74b918797109 149 130 2018-07-03T23:29:35Z Woozle 1 ForkTogether now has its own wiki. wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 27a2cc8c8d0dd0912dd082614f6decebcd1d97fe 151 149 2018-07-25T12:06:48Z Woozle 1 /* Site News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 39e3b2672246a0894f6f626544e48f36e46aa2ca 0 18 112 84 2018-06-14T12:11:14Z Woozle 1 update; other witch domains; corrected toot URL wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Replacements== The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces. The following instances are currently known: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 85430f910470d724f6df97e20d599e78793d9114 150 112 2018-07-18T19:02:54Z Woozle 1 /* Replacements */ wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Replacements== The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces. The following instances are currently known: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 7922c8293ab989d72db6774b9af537d8a4d66b6d 155 150 2018-07-29T12:35:17Z Woozle 1 another category wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:defunct]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. ==Replacements== The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces. The following instances are currently known: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 5ae8b8477c36094ca7bfea5a4a3c57aec0da6dc6 0 168 521 2018-06-22T23:54:12Z Woozle 1 Created page with "This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (accordi..." wikitext text/x-wiki This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooting. 53f02c7d4220450739e63d066f5d0ab6b81c67ac 522 521 2018-06-23T00:11:35Z Woozle 1 wikitext text/x-wiki This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooted (which wasn't strictly necessary, but the system was asking for one because of a kernel upgrade some days ago). 0646c820367e768efcc101a5580a148cef388421 523 522 2018-06-23T00:37:44Z Woozle 1 wikitext text/x-wiki This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooted (which wasn't strictly necessary, but the system was asking for one because of a kernel upgrade some days ago). ...and then it turned out I had forgotten to save my changes before rebooting, so I had to do this: <pre> root@tootcat2:~# systemctl restart mastodon-sidekiq.service Warning: mastodon-sidekiq.service changed on disk. Run 'systemctl daemon-reload' to reload units. sroot@tootcat2:~# systemctl daemon-reload </pre> After finding [https://discourse.joinmastodon.org/t/lots-of-activerecord-connectiontimeouterror/994/3 this explanation], I understood two things: * <code>DB_POOL</code> should be the same as the <code>sidekiq -c</code> value * I actually have plenty of CPU headroom, and can boost this quite a bit more. I first tried 40, and that helped a bit -- but the "busy" queue was still getting stuck around 3500. So then I bumped it up to 100, and within a minute or two the queue was down under 100. e7ca343dcddbf2601d683577f0cb5adea7a5dece 524 523 2018-06-23T00:48:57Z Woozle 1 wikitext text/x-wiki This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooted (which wasn't strictly necessary, but the system was asking for one because of a kernel upgrade some days ago). ...and then it turned out I had forgotten to save my changes before rebooting, so I had to do this: <pre> root@tootcat2:~# systemctl restart mastodon-sidekiq.service Warning: mastodon-sidekiq.service changed on disk. Run 'systemctl daemon-reload' to reload units. root@tootcat2:~# systemctl daemon-reload </pre> After finding [https://discourse.joinmastodon.org/t/lots-of-activerecord-connectiontimeouterror/994/3 this explanation], I understood two things: * <code>DB_POOL</code> should be the same as the <code>sidekiq -c</code> value * I actually have plenty of CPU headroom, and can boost this quite a bit more. I first tried 40, and that helped a bit -- but the "busy" queue was still getting stuck around 3500. So then I bumped it up to 100, and within a minute or two the queue was down under 100. Also, do things in ''this'' order:<pre> root@tootcat2:~# systemctl daemon-reload root@tootcat2:~# systemctl restart mastodon-sidekiq.service </pre> eb5280265607129bd7970e1c05f14b11db1dfb5e 10 43 114 2018-06-26T18:48:36Z Woozle 1 stolen from htyp wikitext text/x-wiki [[issuepedia:{{{1}}}|{{{2|{{{1}}}}}}]] d5e61879517504d52b4ef202290686f259e7e99b 0 44 115 2018-06-26T19:02:15Z Woozle 1 Created page with "Mastodon is pretty effective at preventing trolls, but if they're subtle enough they can manage not to get banned... and other Mastoverse-compatible software seems to encourag..." wikitext text/x-wiki Mastodon is pretty effective at preventing trolls, but if they're subtle enough they can manage not to get banned... and other Mastoverse-compatible software seems to encourage them, somehow. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. ==Proselytizing== {| |- ! User !! Domain !! Software !! Examples |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Assholery== {| |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> 5e364605ec229997b5bd3701fd7f2a17329e5dcb 118 115 2018-06-26T19:06:36Z Woozle 1 wikitext text/x-wiki The primary purpose of this page is to foster a little accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. ==Proselytizing== {| |- ! User !! Domain !! Software !! Examples |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Assholery== {| |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> 33c78afd07a2c0f6cf0f75449146c3ddbf994355 123 118 2018-06-30T11:31:38Z Woozle 1 from a report wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. ==Proselytizing== {| |- ! User !! Domain !! Software !! Examples |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Assholery== {| |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> f61a6cd833ed06ff97bce6f0d7106a7c1a66951f 124 123 2018-06-30T20:11:17Z Woozle 1 one list to out them wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> da53480cf27dec802a16063f7b7dc73462d826c6 125 124 2018-06-30T20:19:03Z Woozle 1 wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> 2713b589cbc0ca25ca2f76c55a09d298cabc4d5a 141 125 2018-07-01T21:05:59Z Woozle 1 ahh yes, much better wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> 378559c960e9663bfb15656edbf9b31025f1fc7b 152 141 2018-07-25T21:02:26Z Woozle 1 wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> f49a19bd945ee7a9a19653d449f93e77e17f4c12 153 152 2018-07-26T12:17:20Z Woozle 1 another, fortunately defunct, dtluna instance wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li.</ref> </references> ba2d678dbabdf5863dc1fc5080e4599b0489f683 10 45 116 2018-06-26T19:04:14Z Woozle 1 stolen from htyp wikitext text/x-wiki [[{{{pfx|{{{2|}}}/}}}{{{1}}}|{{{1}}}]] f792abf1184e294b6c4095ca29ce8767be0ce340 0 16 117 82 2018-06-26T19:04:31Z Woozle 1 wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. Also, have some photos of The {{l/pub|TootCave}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} * {{ld/blog|2018-04-07|sketching a code}} ==Pages== * {{l/sub|malusers}} 226271f355c1e9b7a10c698ed5869672e1766719 0 169 532 531 2018-06-28T10:18:24Z Woozle 1 /* Solved */ 6/28 tidying wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * <s>I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS).</s> ** '''2018-06-28''' This was causing full-page 403 errors for some users; I reverted the Nginx config file and it [https://toot.cat/@news/100281876187861211 seems to be fixed now]. *** commented out the port 80 no-redirect block *** uncommented the old port 80 redirect block *** added an IPv6 listen directive to the uncommented block *** <code>/etc/init.d/nginx reload</code> * <s>A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.)</s> ===Relevant Files=== * <code>/etc/cron.daily/letsencrypt-renew</code> - the [[cron]] job to check/renew the cert * <code>/etc/letsencrypt/renewal/tootcat.conf</code> - Let's Encrypt configuration * <code>/etc/nginx/sites-available/tootcat.conf</code> - Nginx configuration * <code>/var/log/nginx/access.log</code> - Nginx access log (showed 404 when accessing via IPv6) ==Narration / Notes== ===Phase 1=== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ===Phase 2=== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ===Phase 3=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 4=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 5=== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 4c15baafb8c616cb8730338852c9165f35c4dfcc 0 38 119 89 2018-06-28T20:53:34Z Woozle 1 wikitext text/x-wiki The '''Mastoverse''' is the {{l/pub|Mastodon}}-compatible fediverse, i.e. all the federated Mastodon instances as well as instances of other software that federates with Mastodon (including GNUSocial and Pleroma). ==Pages== * {{lc|instances}}: list of instances we have pages about 283e1087873c79a5a2d975e8d03e3d75ca135ad0 0 40 120 102 2018-06-28T20:55:29Z Woozle 1 wikitext text/x-wiki ==Problematicity== ===Arbitrary Decisions=== * '''2018-06-28''' [https://is.a.qute.dog/@KS/703046 Sorting by "most recent activity" immediately shows you that he mass closed every open issue that @hoodie made.] ===Trending Tags=== * '''2018.06.04''' [https://social.coop/@kittybecca/100145873112206294 yesterday apparently the hashtag DropTheT trended on twitter...]: one reason why trending tags is a problematic feature * '''2018.06.03''' ** [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. ** [https://elekk.xyz/@maloki/100141486585398752 What is ForkOff/Together?] * '''2018.06.01-03''' [https://github.com/tootsuite/mastodon/issues/7702 GitHub issue #7702: Admin Option to Disable Trending Feature] ** '''2018.06.03''' [https://mastodon.social/@Gargron/100140965702165118 I've locked the discussion so nobody can comment on it anymore but...] 3199181fb2ef121ca77fc6a9fccd42aff6e775ac 2 6 126 39 2018-06-30T23:24:01Z Woozle 1 wikitext text/x-wiki ==Projects== * [[ForkTogether]] (non-public stuff) ==Situations== * [[witches.town]] ==Dialogues== * [[/octodon.social/@Megan]] 024562f7bce5ab1aefc23de465861b48ad3d6f49 0 47 128 2018-06-30T23:33:13Z Woozle 1 Created page with "==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Soc..." wikitext text/x-wiki ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] 46e2e21b2afa5d0d897e904c4dbfae401f26db2c 129 128 2018-06-30T23:34:46Z Woozle 1 wikitext text/x-wiki ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by Aral Balkan (Mastodon user) bfe9a17a358bc746b1d6f4cda33f51cb0e69197c 131 129 2018-06-30T23:35:50Z Woozle 1 wikitext text/x-wiki The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by Aral Balkan (Mastodon user) 86ddd07efaf6f71e650af6ab24c0b4db9c0facee 132 131 2018-06-30T23:50:12Z Woozle 1 wikitext text/x-wiki The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by Aral Balkan (Mastodon user) ==Technical Resources== * [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" f276cd9ee0dfc970c970dbe4c086342bb176ac76 133 132 2018-07-01T12:28:03Z Woozle 1 wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by Aral Balkan (Mastodon user) ==Technical Resources== * [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" 99436c94d9b14049155d36a69d14d5fbbd80b39a 134 133 2018-07-01T12:58:18Z Woozle 1 wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by Aral Balkan (Mastodon user) ==Technical Resources== * [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" a3f2332fb2094b29dcaf83a054050b9d40834622 136 134 2018-07-01T13:02:05Z Woozle 1 wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by Aral Balkan (Mastodon user) ==Resources== ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Technical''': ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" dd8a9e4cdfbbf2851e3a0d63cd6910bf8d509719 138 136 2018-07-01T14:56:23Z Woozle 1 wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by [https://mastodon.ar.al/@aral/100288153603164066 Aral Balkan] ==Resources== ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Technical''': ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" 0fc4f992b04aa1f74c7da2bdbfabc36aa0d17082 139 138 2018-07-01T16:34:46Z Woozle 1 /* Resources */ wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by [https://mastodon.ar.al/@aral/100288153603164066 Aral Balkan] ==Resources== ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Technical''': ** [https://github.com/GetTogetherComm/GetTogether/issues/60 GetTogether] ([https://mastodon.at/@switchingsocial/100271259537099817 via]) *** {{ls/domain|gettogether.community}}: flagship site ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" 372c3633662371ca5eab58b76b81630105f24160 140 139 2018-07-01T16:37:56Z Woozle 1 /* Other Articles of Interest */ wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by [https://mastodon.ar.al/@aral/100288153603164066 Aral Balkan] * '''2018-06-24''' [https://briarrose.info/2018/06/24/decolonize-co-ops.html Decolonize Co-ops] (by [https://anticapitalist.party/@polymerwitch @polymerwitch]) * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] ==Resources== ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Technical''': ** [https://github.com/GetTogetherComm/GetTogether/issues/60 GetTogether] ([https://mastodon.at/@switchingsocial/100271259537099817 via]) *** {{ls/domain|gettogether.community}}: flagship site ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" 3da42fb64a5c4a341262022a9d8c90bca999b46e 145 140 2018-07-02T11:36:09Z Woozle 1 /* to investigate */ wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by [https://mastodon.ar.al/@aral/100288153603164066 Aral Balkan] * '''2018-06-24''' [https://briarrose.info/2018/06/24/decolonize-co-ops.html Decolonize Co-ops] (by [https://anticapitalist.party/@polymerwitch @polymerwitch]) * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] ==Resources== ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Resources''': ** [https://disroot.org/ Disroot]: "a platform providing online services based on principles of freedom, privacy, federation and decentralization." * '''Technical''': ** [https://github.com/GetTogetherComm/GetTogether/issues/60 GetTogether] ([https://mastodon.at/@switchingsocial/100271259537099817 via]) *** {{ls/domain|gettogether.community}}: flagship site ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" ec6536015a814c11b925da8a7ec49718a518dddc 146 145 2018-07-02T11:38:39Z Woozle 1 /* Resources */ wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by [https://mastodon.ar.al/@aral/100288153603164066 Aral Balkan] * '''2018-06-24''' [https://briarrose.info/2018/06/24/decolonize-co-ops.html Decolonize Co-ops] (by [https://anticapitalist.party/@polymerwitch @polymerwitch]) * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] ==Resources== ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Resources''': ** [https://disroot.org/ Disroot]: "a platform providing online services based on principles of freedom, privacy, federation and decentralization." * '''Technical''': ** [https://github.com/GetTogetherComm/GetTogether/issues/60 GetTogether] ([https://mastodon.at/@switchingsocial/100271259537099817 via]) *** {{ls/domain|gettogether.community}}: flagship site ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" ** Quora: [https://www.quora.com/Are-there-any-actual-open-source-payment-gateways-not-just-a-library-that-integrates-with-other-payment-gateways Are there any actual open source payment gateways, not just a library that integrates with other payment gateways?] 45bccd48c9a017c3e91ad739f1a456ef66760576 147 146 2018-07-02T11:42:55Z Woozle 1 wikitext text/x-wiki __NOTOC__ The first official meeting of the ForkTogether group took place on June 30, 2018. The group will be reconvening on July 8 to finish going through the agenda. ==Official Documents== * [https://cloud.vbz.net/index.php/s/XKpxgsPnDSdd58H WIP First Meeting] (copied 2018-07-01) ==Posts from Attendees== * '''2018-06-30''' [https://medium.com/@uistephen/first-together-meeting-reflections-a355b07b6ec1 First #Together meeting thoughts] ==Community Backgrounders== * '''2018-06-25''' [https://medium.com/@novemberninerniner/polls-general-requests-and-social-activism-7ba51eebddaa Polls, General Requests, and Social Activism] by Hoodie * '''2018-06-26''' [https://medium.com/@novemberninerniner/user-expectations-software-design-and-when-breaking-these-rules-of-interaction-can-be-acceptable-565e677d6f43 User Expectations, Software Design, and when breaking these rules of interaction can be acceptable] by Hoodie * '''2018-06-29''' [https://medium.com/@novemberninerniner/structuring-your-open-source-project-for-the-purposes-of-accessibility-social-activism-6b1d7fe6c97d Structuring your Open Source project for the purposes of Accessibility & Social Activism] by Hoodie ** [https://trello.com/b/Kq1YOpGt/accessiblity-and-social-activism-oriented-development Trello board] ==Other Articles of Interest== * '''2018-06-29''' [https://ar.al/2018/06/29/reclaiming-rss/ Reclaiming RSS] by [https://mastodon.ar.al/@aral/100288153603164066 Aral Balkan] * '''2018-06-24''' [https://briarrose.info/2018/06/24/decolonize-co-ops.html Decolonize Co-ops] (by [https://anticapitalist.party/@polymerwitch @polymerwitch]) * '''2018-06-23''' [https://techcrunch.com/2018/06/23/open-source-sustainability/ Open source sustainability] ==Resources== ===member-provided=== ''resources operated by members and available for FT use'' * Nextcloud on {{ls/domain|cloud.vbz.net}} (Woozle) * Redmine on {{ls/domain|rm.vbz.net}} (Woozle) * Hubzilla on {{ls/domain|hub.iseeamess.com}} (Woozle) ===to investigate=== * '''Community-Building''': ** [https://opencollective.com/ OpenCollective] * '''Resources''': ** [https://disroot.org/ Disroot]: "a platform providing online services based on principles of freedom, privacy, federation and decentralization." * '''Technical''': ** [https://github.com/GetTogetherComm/GetTogether/issues/60 GetTogether] ([https://mastodon.at/@switchingsocial/100271259537099817 via]) *** {{ls/domain|gettogether.community}}: flagship site ** [https://github.com/puckipedia/Kroeg Kroeg]: "An ActivityPub server in C#" ** Quora: [https://www.quora.com/Are-there-any-actual-open-source-payment-gateways-not-just-a-library-that-integrates-with-other-payment-gateways Are there any actual open source payment gateways, not just a library that integrates with other payment gateways?] b87298b738542a728c965c41f2e3409e189a3919 148 147 2018-07-03T23:27:43Z Woozle 1 moved to new wiki wikitext text/x-wiki Everything that was here has been moved to [https://forktogether.space/mw/Main_Page the forktogether.space wiki]. b02a01b6717e3e3eda460362f1e888a07806daca 4 10 143 23 2018-07-02T10:36:57Z Woozle 1 cat-related instances wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lpub/user|woozle}}, sysadmin of [[toot.cat]] (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any profile information you enter on Mew (including, notably, your email address) will be accessible to database sysops (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki). * '''Warrant Canary''': in the event of a subpoena, we will follow our conscience as regards how much to reveal both to authorities and to the community. We have not received any such requests as of this writing, and (at a minimum) this sentence will be removed in the event that we do. ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. ==Related== Other sites with a cat theme: * {{ls/domain|kitty.town}}: recommended; high standards for safe space * {{ls/domain|meow.social}}:furry-oriented ==History== * '''2018-03-30''' (Fri) Installed MediaWiki last night and got it mostly configured; got image uploads working and some explanatory content; still trying to figure out a good way to have some pages public and most pages not. b62d61ac8692e564b5fba64723fc7fb6cbc4b865 144 143 2018-07-02T10:37:06Z Woozle 1 /* Related */ wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lpub/user|woozle}}, sysadmin of [[toot.cat]] (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any profile information you enter on Mew (including, notably, your email address) will be accessible to database sysops (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki). * '''Warrant Canary''': in the event of a subpoena, we will follow our conscience as regards how much to reveal both to authorities and to the community. We have not received any such requests as of this writing, and (at a minimum) this sentence will be removed in the event that we do. ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. ==Related== Other sites with a cat theme: * {{ls/domain|kitty.town}}: recommended; high standards for safe space * {{ls/domain|meow.social}}: furry-oriented ==History== * '''2018-03-30''' (Fri) Installed MediaWiki last night and got it mostly configured; got image uploads working and some explanatory content; still trying to figure out a good way to have some pages public and most pages not. 34846e965571cfeea7159daa626dad2d0a58acf2 154 144 2018-07-29T12:34:05Z Woozle 1 wikitext text/x-wiki ==Basics== * '''Ownership''': Mew is operated and hosted by {{lpub/user|woozle}}, sysadmin of {{l/pub|toot.cat}} (hopefully soon to be joined by a team of others from across the fediverse). * '''Code of Conduct''': [https://toot.cat/about/more toot.cat's CoC] will be enforced here as well. * '''Disclosure''': Any profile information you enter on Mew (including, notably, your email address) will be accessible to database sysops (currently woozle alone, but this may change), although not accessible to admins of Mew (the wiki). * '''Warrant Canary''': in the event of a subpoena, we will follow our conscience as regards how much to reveal both to authorities and to the community. We have not received any such requests as of this writing, and (at a minimum) this sentence will be removed in the event that we do. ==Purpose== This site is a compromise. There are some [[/wishlist/tools|specific tools]] I wanted to have in place first, but the need for something like this appears too urgent to wait any longer. The social fediverse (of which Mastodon is currently by far the largest piece) needs '''anchors''' &ndash; reference points that don't just flash by in a stream and become practically impossible to find. This wiki is a first-pass at providing an anchor, and for exploring and modelling methods of doing that. ==Related== Other sites with a cat theme: * {{ls/domain|kitty.town}}: recommended; high standards for safe space * {{ls/domain|meow.social}}: furry-oriented ==History== * '''2018-03-30''' (Fri) Installed MediaWiki last night and got it mostly configured; got image uploads working and some explanatory content; still trying to figure out a good way to have some pages public and most pages not. 49cafebf8dacecc898b3ae616f341e75e5dab030 0 167 519 2018-07-19T00:44:05Z Woozle 1 Created page with "This is going to involve some experimentation, as I've never used Amazon services before and don't intend to start until they reform (not expecting this to happen). My curren..." wikitext text/x-wiki This is going to involve some experimentation, as I've never used Amazon services before and don't intend to start until they reform (not expecting this to happen). My current plan is: # Use [[rclone]] ([https://rclone.org/ web]) to determine how much space current media takes up. # Ensure I have a volume or "space" on DigitalOcean sufficient to accommodate that amount. # Use rclone to copy the media over. # Reconfigure toot.cat's Mastodon to point at the new location. # Leave this configuration in place for a few days, looking for issues and making sure everything is being served by the new location. # Tell PolymerWitch she can turn off the Amazon service, at long last. b1836754d4695d5f42ba9b596b7d2fe7c5a66f69 0 48 156 2018-07-29T13:09:16Z Woozle 1 mainly just needed a place to stash the #osb17 link, but I'll probably find more to put here, over time wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] #osb17 = [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition]. 68d9414f48e9064956c05ba5609e73c9e70c2261 158 156 2018-07-29T13:36:00Z Woozle 1 a bit more wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ac70db60c914296430de11f57bb5ca1bc49ae85f 10 49 157 2018-07-29T13:35:25Z Woozle 1 from forktogether wikitext text/x-wiki [https://{{{2}}}/@{{{1}}} ''@''{{{1}}}''@''{{{2}}}] 3d2274248ecdeba8916b444b59752adc6c1f9949 0 1 159 151 2018-08-15T22:55:21Z Woozle 1 /* Site News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, and are currently compiling Ruby with jemalloc for improved performance. Please pardon the downtime! * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 25c3586cb286625811dda7d55063aa00a1d51224 160 159 2018-08-15T23:10:51Z Woozle 1 /* Site News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, and are currently compiling Ruby with jemalloc for improved performance. Please pardon the downtime! ** Apparently its the Gems that take most of the time. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> ab83137c748f0e289021e968fed4ff328375253f 161 160 2018-08-15T23:59:43Z Woozle 1 /* Site News */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 1f18488741bc16456dbd8f0e18151e4289c55dd9 167 161 2018-08-17T13:34:57Z Woozle 1 toot.cat, cats wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for {{l/pub|toot.cat}}, and we have started a repository of {{l/pub|cat}}-related things on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 24f27ab49433f8191667a5aa1db0a7aa0bdf0ca8 175 167 2018-08-17T21:29:59Z Woozle 1 /* Welcome to Me{{grey|dia}}W{{grey|iki}}! */ better text for link, and more emphasis of links wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 1725d960fd960f38b18b2079f51fbc1aa8602b22 187 175 2018-10-09T21:46:52Z Woozle 1 directories wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> b4b8a17ae7686e49b77b60d3bea89826f32c815d 190 187 2018-10-11T12:33:37Z Woozle 1 /* Site News */ Hubzilla wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 9f6a2b8db3d1cb49e6d4b76e4974c2d0384efa75 200 190 2019-04-07T17:08:32Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 7f1e4971054f95b3cf8dd3a411ff92230a4a8af2 10 14 162 22 2018-08-17T13:15:21Z Woozle 1 Woozle moved page [[Template:Lpub/user]] to [[Template:L/pub/user]]: consistency wikitext text/x-wiki [[pub/user/{{{1}}}|{{{1}}}]] 5134ca0ddd9b0b95f42bc8bb78b7b80f548ebeab 10 50 163 2018-08-17T13:15:21Z Woozle 1 Woozle moved page [[Template:Lpub/user]] to [[Template:L/pub/user]]: consistency wikitext text/x-wiki #REDIRECT [[Template:L/pub/user]] 58e424478aa60c552c4654e0b05c5a68ebaa3a81 10 51 164 2018-08-17T13:29:55Z Woozle 1 Created page with "[https://toot.cat/tags/{{{1}}} {{{1}}}]" wikitext text/x-wiki [https://toot.cat/tags/{{{1}}} {{{1}}}] 695d1e2e252e81a2b40884142c443af641eb57f2 165 164 2018-08-17T13:30:27Z Woozle 1 wikitext text/x-wiki [https://toot.cat/tags/{{{1}}} #{{{1}}}] c6d218adf6eaacf0d1a40b15b25f36416e609ea4 0 52 166 2018-08-17T13:30:51Z Woozle 1 Created page with "Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting..." wikitext text/x-wiki Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://meow.social/@netkitty kitten.exe] (Mastodon account) * {{l/hashtag|cats}} 5c52c4daefc5508f80663e45600253dcf602aae9 169 166 2018-08-17T13:37:13Z Woozle 1 Mastodon is a cat-sharing site. wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://meow.social/@netkitty kitten.exe] (Mastodon account) * {{l/hashtag|cats}} f853ab8560ed7a60029c953ba230544f3a52ed77 170 169 2018-08-17T13:38:43Z Woozle 1 header wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://meow.social/@netkitty kitten.exe] (Mastodon account) * {{l/hashtag|cats}} 97d942e625eaf8fb344d24b752de7dbd8f059988 171 170 2018-08-17T13:43:35Z Woozle 1 /* Tooting Cat Accounts on TootCat */ wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://meow.social/@netkitty kitten.exe] (Mastodon account) * {{l/hashtag|cats}} 9e37e1bfdfabe0ca45d51902d039d61256338e77 173 171 2018-08-17T17:32:25Z Woozle 1 /* Other Items */ update wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" 5365adc093dce9ecff0a37d0aeb48b1a4da83807 176 173 2018-08-17T21:31:34Z Woozle 1 wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" c852772a90db300d4ec47957334e13beb2367f01 177 176 2018-08-18T12:00:49Z Woozle 1 rarity wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" d66d69b9645b0e105d61f3d849241b04077b35f7 178 177 2018-08-18T23:09:45Z Woozle 1 wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@meowra meowra] (Onyx and Rudy) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@oscelot Oscelot] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" dcf080774cd8f4b485f005a8825a7b3827db0cf1 179 178 2018-08-21T00:15:08Z Woozle 1 /* Tooting Cat Accounts on TootCat */ wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@meowra meowra] (Onyx and Rudy) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ===not actual cats?=== * [https://toot.cat/@oscelot Oscelot] -- [https://toot.cat/@oscelot/100585328496929184 claims] not to be cat-related, but profile also says "cat". We are confused. ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" 2b01b58ee8739e37d08b87bf566e15c694ada188 180 179 2018-08-30T00:52:02Z Woozle 1 more catstuff wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since {{l/pub|toot.cat}} is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@eddy Eddy] (a smol orange tabby girl cat) * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@Lady Lady] (a bicolor medium-length street cat with feline herpes) * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@meowra meowra] (Onyx and Rudy) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ===cat people=== * [https://toot.cat/@KittyMinT mint] "im mint and im like cats." * [https://toot.cat/@oscelot Oscelot] -- [https://toot.cat/@oscelot/100585328496929184 claims] not to be cat-related, but profile also says "cat". We are confused. ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" 511501e36b7f62c61fa143d9b0eca5203f078cff 6 53 168 2018-08-17T13:35:58Z Woozle 1 * '''what''': new user reaction to Mastodon * '''retrieved''': 2018-08-17 09:35 EDT wikitext text/x-wiki * '''what''': new user reaction to Mastodon * '''retrieved''': 2018-08-17 09:35 EDT a9ccfe5098145838586242872499389669dd91bf 0 48 172 158 2018-08-17T17:30:51Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] d7d933a1a950a06a9c502240af4d8807d155de93 189 172 2018-10-11T12:30:12Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}. ==Information== * [[/block list]] ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] 86aa016c92fb3e6c37a16aa074aa9619b26861b6 10 15 174 25 2018-08-17T21:29:20Z Woozle 1 wikitext text/x-wiki [[pub/{{{1}}}|{{{2|{{{1}}}}}}]] 4de9d7b4d48aa22b323276ec06f6c52329975ef6 0 166 517 2018-08-25T16:20:27Z Woozle 1 Created page with "==from Discord== <poem> http://tootcat2.hypertwins.net/.well-known/acme-challenge/nLguP2F142gk3WBcZm4BSF86dEp6zMs8_5nmHXADpuM is returning a 404, and just quickly I can't tell..." wikitext text/x-wiki ==from Discord== <poem> http://tootcat2.hypertwins.net/.well-known/acme-challenge/nLguP2F142gk3WBcZm4BSF86dEp6zMs8_5nmHXADpuM is returning a 404, and just quickly I can't tell where the actual file is supposed to be. I'll look at it later, hopefully in a couple of hours, if I get a chance, but thought I should give you a heads-up just in case. Saving debug log to /var/log/letsencrypt/letsencrypt.log WoozleToday at 10:01 AM Looking into this now. The problem may be on the file-writing site... though I'm getting conflicting information... Nginx is giving me the same problem Apache gives me: I can't tell what file it's trying to access in response to the URL. WoozleToday at 11:13 AM Okay, so... there's a Nginx directive that's not working as intended, and figuring out directive syntax is one of my major weak spots. This:<pre> location ^~ /.well-known/acme-challenge/ { root /var/www/challenges; }</pre> ...seems like it's supposed to strip out the /.well-known/acme-challenge/ from the URL, and append whatever's left to /var/www/challenges. So http://tootcat2.hypertwins.net/.well-known/acme-challenge/test.txt would result in an access to /var/www/challenges/test.txt. But it's not; it's actually resulting in an access to /var/www/challenges/.well-known/acme-challenge/test.txt. But this is a location I can work with, so I'm not going to try to understand the location directive beyond noting that this is how it is effectively working. The next problem is that the certbot seems to be failing to create the test file... unless it is deleting it after the test fails, but from what I remember it doesn't do that; it leaves the files in place for diagnostic purposes. And the most recent test files are from back in May. I changed the certbot config in Webmin so it points directly to /var/www/challenges/.well-known/acme-challenge/, and that seems to have worked. ...but Firefox still says toot.cat's SSL expires on Aug. 28. Maybe I have to restart nginx again? Or restart Mastodon? Dang, what's that command to check a cert from the CLI... openssl something, I think... Oh good, I made notes: https://htyp.org/openssl openssl s_client -connect toot.cat:443 -- okay, great, gives me lots of info that does not include the expiration date. The secret code phrase is apparently: echo | openssl s_client -connect toot.cat:443 2>/dev/null | openssl x509 -noout -dates ...and this confirms that the expiry is still 3 days from now. WoozleToday at 12:01 PM Got it. I'm not sure if Let's Encrypt will renew properly next time, though; the config was clearly kind of messed up. I tried to tidy it, but I'm guessing about some pieces. </poem> 03916e7fd54bdce5f7bf539e069d35fcc9c7ca8d 0 54 181 2018-10-05T19:18:10Z Woozle 1 Created page with "[[category:instances]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} Rel..." wikitext text/x-wiki [[category:instances]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} 796c3b9ed29bab9d5f4779a074a15acfd4b9b40d 183 181 2018-10-05T19:20:44Z Woozle 1 Woozle moved page [[Witches]] to [[Pub/witches]] without leaving a redirect: meant to be public wikitext text/x-wiki [[category:instances]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} 796c3b9ed29bab9d5f4779a074a15acfd4b9b40d 185 183 2018-10-05T19:23:47Z Woozle 1 witches.live wikitext text/x-wiki [[category:instances]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} * {{ls/domain|witches.live}} "a mastodon instance for witches" Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} 0d9e2c660d00c4e81e2b3226a806268bf71ca1f4 0 18 182 155 2018-10-05T19:18:44Z Woozle 1 extracted list of witch-instances to its own page wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:defunct]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces; see [[witches]] for a list. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 0f0a040eff4969daa3a5faff05667813ba78331a 184 182 2018-10-05T19:21:16Z Woozle 1 public link wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:defunct]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces; see {{l/pub|witches}} for a list. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 454a905562c8518cf18a462c97cbb1c684573ea1 0 44 186 153 2018-10-07T11:44:52Z Woozle 1 update wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li. '''Update 2018-10-07''': They have now been blocked after a report from a known user.</ref> </references> 903237b5bd1689d951050a14b2d2f8dbeca35e76 0 55 188 2018-10-11T12:29:18Z Woozle 1 Created page with "Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): <pre> rainbowdash.net Suspend shitpos..." wikitext text/x-wiki Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): <pre> rainbowdash.net Suspend shitposter.club Suspend social.headsca.la Suspend woofer.alfter.us Suspend social.au2pb.net Suspend gorf.club Suspend sealion.club Suspend gs.smuglo.li Suspend unsafe.space Suspend wrongthink.net Suspend social.troll.academy Silence social.heldscal.la Silence pawoo.net Silence freezepeach.xyz Silence anitwitter.com Silence wogan.im Suspend noagendasocial.com Silence mstdn.jp Silence ediot.social Suspend community.highlandarrow.com Suspend social.tchncs.de Silence admins.town Silence post.mashek.net Suspend gs.archae.me Silence pridelands.io Suspend hiveway.net Silence polycule.club Suspend eroma.rareome.ga Suspend loli.estate Suspend raki.social Suspend pl.smuglo.li Suspend newjack.city Suspend </pre> 6ac00757ae1b8a17be8ff2be9753287b65638ed6 203 188 2019-04-23T20:56:48Z Woozle 1 wikitext text/x-wiki Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): * socialnetwork.ninja - blocked 2019-04-23 because information indicated the instance is run by a police officer <pre> rainbowdash.net Suspend shitposter.club Suspend social.headsca.la Suspend woofer.alfter.us Suspend social.au2pb.net Suspend gorf.club Suspend sealion.club Suspend gs.smuglo.li Suspend unsafe.space Suspend wrongthink.net Suspend social.troll.academy Silence social.heldscal.la Silence pawoo.net Silence freezepeach.xyz Silence anitwitter.com Silence wogan.im Suspend noagendasocial.com Silence mstdn.jp Silence ediot.social Suspend community.highlandarrow.com Suspend social.tchncs.de Silence admins.town Silence post.mashek.net Suspend gs.archae.me Silence pridelands.io Suspend hiveway.net Silence polycule.club Suspend eroma.rareome.ga Suspend loli.estate Suspend raki.social Suspend pl.smuglo.li Suspend newjack.city Suspend </pre> 071470efa574f97313910893f59f7080e80a125b 204 203 2019-04-23T20:57:49Z Woozle 1 wikitext text/x-wiki Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): * socialnetwork.ninja - blocked 2019-04-23 because information indicated the instance is run by a police officer * bsd.moe <pre> rainbowdash.net Suspend shitposter.club Suspend social.headsca.la Suspend woofer.alfter.us Suspend social.au2pb.net Suspend gorf.club Suspend sealion.club Suspend gs.smuglo.li Suspend unsafe.space Suspend wrongthink.net Suspend social.troll.academy Silence social.heldscal.la Silence pawoo.net Silence freezepeach.xyz Silence anitwitter.com Silence wogan.im Suspend noagendasocial.com Silence mstdn.jp Silence ediot.social Suspend community.highlandarrow.com Suspend social.tchncs.de Silence admins.town Silence post.mashek.net Suspend gs.archae.me Silence pridelands.io Suspend hiveway.net Silence polycule.club Suspend eroma.rareome.ga Suspend loli.estate Suspend raki.social Suspend pl.smuglo.li Suspend newjack.city Suspend </pre> a9b00bdd67651b8242eb6262326c7ffd81085ebb 0 56 191 2018-11-19T01:28:58Z Woozle 1 Created page with "some cover songs possibly in Catalan (hey, it's all I've been able to find so far!): * [https://www.youtube.com/watch?v=Bw6Q9GiVaYw Mr Tambourine Man - Todo Tiene Su Sitio Baj..." wikitext text/x-wiki some cover songs possibly in Catalan (hey, it's all I've been able to find so far!): * [https://www.youtube.com/watch?v=Bw6Q9GiVaYw Mr Tambourine Man - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=t17tD0ByhR4 500 Millas - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] ==Reference== * [[wikipedia:Catalan language|Wikipedia]] 44fe204f58b163719067d16c00063ed177d376e5 193 191 2018-11-19T01:30:05Z Woozle 1 wikitext text/x-wiki some cover songs possibly in Catalan (hey, it's all I've been able to find so far!): * [https://www.youtube.com/watch?v=Bw6Q9GiVaYw Mr Tambourine Man - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=t17tD0ByhR4 500 Millas - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=GFav2hjkLjE 12. Arriba la nit - Txarango] ==Reference== * [[wikipedia:Catalan language|Wikipedia]] 70f2af60dcbaa88a752c8af80e7c5604ba137ca6 194 193 2018-11-19T01:34:39Z Woozle 1 wikitext text/x-wiki some cover songs possibly in Catalan (hey, it's all I've been able to find so far!): * [https://www.youtube.com/watch?v=Bw6Q9GiVaYw Mr Tambourine Man - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=t17tD0ByhR4 500 Millas - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=GFav2hjkLjE 12. Arriba la nit - Txarango] * [https://www.youtube.com/watch?v=e2pEx7PAb30 Txarango - Agafant l'horitzó (ft. G. Humet, Aspencat, C. Freixas, Les Kol·lontai i Ascensa Furore)] ==Reference== * [[wikipedia:Catalan language|Wikipedia]] 5457bbb7f2c9bc6d84197341d30f08e4b20b7377 0 42 192 109 2018-11-19T01:29:08Z Woozle 1 Catalan wikitext text/x-wiki The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about {{l/pub|Catalonia}} as it comes our way. * We are interested in making space for content related to Catalonia and/or {{l/pub|Catalan}}. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Mastodon user Sam Toland [https://social.coop/@samtoland/100152739177441119 notes] that the .cat admins used to be much stricter, but have now loosened enforcement a bit. 29f999bb704d5b129c3dc3e1e2e0e12227cebfeb 0 57 195 2019-01-25T15:10:00Z Woozle 1 Created page with "==About== '''text2toot''' is a connector which allows posting to Mastodon via texting from your phone. It was written by ash on 2019-01-25 and the source code is available [ht..." wikitext text/x-wiki ==About== '''text2toot''' is a connector which allows posting to Mastodon via texting from your phone. It was written by ash on 2019-01-25 and the source code is available [https://github.com/ashkitten/text2toot on GitHub]. It requires Twilio, or some other similar phone system back-end, to send and receive the texts. In theory, it can be used with any instance. More detailed setup instructions will be added as soon as I can. ==Syntax== * (no command, media attached) *: uploads media to instance for inclusion in next toot * clear_media *: clears currently pending attachments * post.visibility[content warning] post content *: sends toot, additionally including any pending media ** visibility is optional; defaults to global ** content warning is optional; defaults to none * register [instance] [token] *: sets current login * notify subscribe *: subscribes to mention notifications * notify unsubscribe *: unsubscribes from mention notifications a555c76445d526d1bb37e0070499bbaf11f7e55c 197 195 2019-01-25T15:12:30Z Woozle 1 wikitext text/x-wiki ==About== '''text2toot''' is a connector which allows posting to Mastodon via texting from your phone. It was written by ash on 2019-01-25 and the source code is available [https://github.com/ashkitten/text2toot on GitHub]. It requires Twilio, or some other similar phone system back-end, to send and receive the texts. In theory, it can be used with any instance. More detailed setup instructions will be added as soon as I can. ==Syntax== * (no command, media attached) *: uploads media to instance for inclusion in next toot * clear_media *: clears currently pending attachments * post.visibility<nowiki>[[content warning]]</nowiki> post content *: sends toot, additionally including any pending media ** visibility is optional; defaults to global ** content warning is optional; defaults to none * register [instance] [token] *: sets current login * notify subscribe *: subscribes to mention notifications * notify unsubscribe *: unsubscribes from mention notifications fde16f3c356c5ddf1333802d164d44511197940b 12 3 196 59 2019-01-25T15:12:02Z Woozle 1 text2toot wikitext text/x-wiki More help stuff needs to go here, but for now... ==Mastodon== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ===features=== * {{l/pub|text2toot}} (experimental) ==Mew== * [[Help:Admin]]: wiki administration help f1e298362eb202f1c917b0c8dc4ad40aaf8488b0 0 165 514 2019-02-10T18:54:41Z Woozle 1 Created page with "<pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker"..." wikitext text/x-wiki <pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' Feb 10 18:51:15 tootcat2 sshd[7271]: Connection closed by 118.25.110.158 port 37586 [preauth] Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.308Z 30030 TID-owp9kkfe6 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.311Z 30030 TID-owp9kkfe6 WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.313Z 30030 TID-owp9kkfe6 WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.953Z 30030 TID-gphwttvbm WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.954Z 30030 TID-gphwttvbm WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.955Z 30030 TID-gphwttvbm WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.176Z 30030 TID-gphwjiv5e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.177Z 30030 TID-gphwjiv5e WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.178Z 30030 TID-gphwjiv5e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:23 tootcat2 sshd[7349]: Invalid user hate from 194.44.154.76 port 26361 Feb 10 18:52:24 tootcat2 sshd[7349]: Received disconnect from 194.44.154.76 port 26361:11: Bye Bye [preauth] Feb 10 18:52:24 tootcat2 sshd[7349]: Disconnected from invalid user hate 194.44.154.76 port 26361 [preauth] Feb 10 18:52:31 tootcat2 sshd[7358]: Connection closed by 218.161.34.78 port 58004 [preauth] Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.521Z 30030 TID-owp6t798e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.584Z 30030 TID-owp6t798e WARN: Stoplight::Error::RedLight: Delivery failed for https://osada.usezot.net/inbox: https://osada.usezot.net/inbox Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.736Z 30030 TID-owp6t798e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.122Z 30030 TID-owpcdbkfq WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' </pre> a4a6beb450e56e99fe98f8e8c531f61562416858 515 514 2019-02-10T18:57:08Z Woozle 1 wikitext text/x-wiki I'm not sure any of this is actually related to the problem... no mention of the user in question. <pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' Feb 10 18:51:15 tootcat2 sshd[7271]: Connection closed by 118.25.110.158 port 37586 [preauth] Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.308Z 30030 TID-owp9kkfe6 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.311Z 30030 TID-owp9kkfe6 WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.313Z 30030 TID-owp9kkfe6 WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.953Z 30030 TID-gphwttvbm WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.954Z 30030 TID-gphwttvbm WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.955Z 30030 TID-gphwttvbm WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.176Z 30030 TID-gphwjiv5e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.177Z 30030 TID-gphwjiv5e WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.178Z 30030 TID-gphwjiv5e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:23 tootcat2 sshd[7349]: Invalid user hate from 194.44.154.76 port 26361 Feb 10 18:52:24 tootcat2 sshd[7349]: Received disconnect from 194.44.154.76 port 26361:11: Bye Bye [preauth] Feb 10 18:52:24 tootcat2 sshd[7349]: Disconnected from invalid user hate 194.44.154.76 port 26361 [preauth] Feb 10 18:52:31 tootcat2 sshd[7358]: Connection closed by 218.161.34.78 port 58004 [preauth] Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.521Z 30030 TID-owp6t798e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.584Z 30030 TID-owp6t798e WARN: Stoplight::Error::RedLight: Delivery failed for https://osada.usezot.net/inbox: https://osada.usezot.net/inbox Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.736Z 30030 TID-owp6t798e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.122Z 30030 TID-owpcdbkfq WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' </pre> ec7166dc087fbb9de402ee5c27621bcc212a7329 0 58 198 2019-03-05T16:03:26Z Woozle 1 Created page with "[[category:instances]] May be run by an FBI informant? See [https://dragon.style/@packbat/101694219419341628 this]." wikitext text/x-wiki [[category:instances]] May be run by an FBI informant? See [https://dragon.style/@packbat/101694219419341628 this]. e275bfc3da82717cd4ca1dd7de60a8cc45cb347e 10 59 199 2019-04-07T17:07:28Z Woozle 1 Created page with "[[:category:{{{1}}}|{{{2|{{{1}}}}}}]]" wikitext text/x-wiki [[:category:{{{1}}}|{{{2|{{{1}}}}}}]] 4df43003181f58431903e9c3ccfbaf15e8e2a321 0 60 201 2019-04-07T17:12:46Z Woozle 1 Created page with "[[category:instances]] A strange instance with no descriptor; trying to figure out what they're up to. * [https://daffodil-11.org/@pleasetouch_me @pleasetouch_me] followed me..." wikitext text/x-wiki [[category:instances]] A strange instance with no descriptor; trying to figure out what they're up to. * [https://daffodil-11.org/@pleasetouch_me @pleasetouch_me] followed me on Hubzilla. Kind of creepy name. * [https://daffodil-11.org/@moanlisa @moanlisa] - followbot? * [https://daffodil-11.org/@gunner @gunner] - followbot? 690efd74903db09aa6b11cd4c63ddfc3452abfe9 202 201 2019-04-23T20:53:17Z Woozle 1 wikitext text/x-wiki [[category:instances]] A strange instance with no descriptor; trying to figure out what they're up to. * [https://daffodil-11.org/@pleasetouch_me @pleasetouch_me] followed me on Hubzilla. Kind of creepy name. * [https://daffodil-11.org/@moanlisa @moanlisa] - followbot? user report: "Every account on this instance is mass-following people." * [https://daffodil-11.org/@gunner @gunner] - followbot? ebbc477d6a6c6149f65af7f7554a58d345199a49 0 16 205 117 2019-05-30T13:42:08Z Woozle 1 wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. Also, have some photos of The {{l/pub|TootCave}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} * {{ld/blog|2018-04-07|sketching a code}} ==Pages== * {{l/sub|GlitchSoc}}: feature requests * {{l/sub|malusers}} 035507fda19b47662f66b5f3bbdfe4ebab41b307 0 61 206 2019-05-30T13:43:58Z Woozle 1 Created page with "==Feature Requests== ===moderation panel=== * option to message the reporting user as part of the moderation action * should be a link to the problem user's stream * (large) r..." wikitext text/x-wiki ==Feature Requests== ===moderation panel=== * option to message the reporting user as part of the moderation action * should be a link to the problem user's stream * (large) retain deleted information somewhere, preferably in reinstateable form (don't destroy the evidence!) 62907bdabb3f959f4b8d2af60557e52d9c194f5f 207 206 2019-05-30T14:34:19Z Woozle 1 wikitext text/x-wiki ==Feature Requests== ===moderation panel=== * option to message the reporting user as part of the moderation action * should be a link to the problem user's stream * (large) retain deleted information somewhere, preferably in reinstateable form (don't destroy the evidence!) ===admin options=== * option for admins to get notifs (in web UI, not just email) of reports * option for admins to get notifs of new signups * somehow streamline the process so that multiple accounts can be silenced ** maybe a list, in admin, of accounts by signup date, with easy links to moderation panel *** preferably also a way to make notes on each user, visible only to other admins c252e48eb03b0da09b51f703c3f89ffac5efb143 208 207 2019-06-17T18:39:26Z Woozle 1 wikitext text/x-wiki ==Feature Requests== ===moderation panel=== * option to save a note when taking an action (right now, can only do these one at a time) * option to message the reporting user as part of the moderation action * should be a link to the problem user's stream * (large) retain deleted information somewhere, preferably in reinstateable form (don't destroy the evidence!) ===admin options=== * option for admins to get notifs (in web UI, not just email) of reports * option for admins to get notifs of new signups * somehow streamline the process so that multiple accounts can be silenced ** maybe a list, in admin, of accounts by signup date, with easy links to moderation panel *** preferably also a way to make notes on each user, visible only to other admins 3d7a5162c27bff1ed0a8f6158cbb54b7639f69cc 0 55 209 204 2019-08-18T14:21:42Z Woozle 1 Fedichive wikitext text/x-wiki * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340] * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): <pre> rainbowdash.net Suspend shitposter.club Suspend social.headsca.la Suspend woofer.alfter.us Suspend social.au2pb.net Suspend gorf.club Suspend sealion.club Suspend gs.smuglo.li Suspend unsafe.space Suspend wrongthink.net Suspend social.troll.academy Silence social.heldscal.la Silence pawoo.net Silence freezepeach.xyz Silence anitwitter.com Silence wogan.im Suspend noagendasocial.com Silence mstdn.jp Silence ediot.social Suspend community.highlandarrow.com Suspend social.tchncs.de Silence admins.town Silence post.mashek.net Suspend gs.archae.me Silence pridelands.io Suspend hiveway.net Silence polycule.club Suspend eroma.rareome.ga Suspend loli.estate Suspend raki.social Suspend pl.smuglo.li Suspend newjack.city Suspend </pre> d5cbe5786dd742af5618d9386ae64aa560bfb85a 210 209 2019-08-18T14:50:59Z Woozle 1 wikitext text/x-wiki * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): <pre> rainbowdash.net Suspend shitposter.club Suspend social.headsca.la Suspend woofer.alfter.us Suspend social.au2pb.net Suspend gorf.club Suspend sealion.club Suspend gs.smuglo.li Suspend unsafe.space Suspend wrongthink.net Suspend social.troll.academy Silence social.heldscal.la Silence pawoo.net Silence freezepeach.xyz Silence anitwitter.com Silence wogan.im Suspend noagendasocial.com Silence mstdn.jp Silence ediot.social Suspend community.highlandarrow.com Suspend social.tchncs.de Silence admins.town Silence post.mashek.net Suspend gs.archae.me Silence pridelands.io Suspend hiveway.net Silence polycule.club Suspend eroma.rareome.ga Suspend loli.estate Suspend raki.social Suspend pl.smuglo.li Suspend newjack.city Suspend </pre> 4b78b5ed797df3dfc314071dc2de2319d2ef5260 224 210 2019-12-30T20:00:19Z Woozle 1 current block list, before change wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==change history== * '''2019-12-30''' removing silence from <code>social.tchncs.de</code> because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced ==active blocks== * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |social.tchncs.de |silenced |1.34K |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} a3d90a7fc8485acb8b15a06e5af99fba54107234 225 224 2019-12-30T20:05:46Z Woozle 1 clarification that this was done after consultation wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==change history== * '''2019-12-30''' After discussion with the admin team, we're removing silence from <code>social.tchncs.de</code> because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. ==active blocks== * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |social.tchncs.de |silenced |1.34K |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 5c78e42f0c2005c4e173998e8059d8e4aff33864 226 225 2019-12-30T20:06:45Z Woozle 1 /* active blocks */ removed social.tchncs.de from list wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==change history== * '''2019-12-30''' After discussion with the admin team, we're removing silence from <code>social.tchncs.de</code> because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. ==active blocks== * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} d55264e379af7cbb92b5ffebe82faf1353c3f53f 227 226 2019-12-30T20:10:13Z Woozle 1 /* active blocks */ wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==change history== * '''2019-12-30''' After discussion with the admin team, we're removing silence from <code>social.tchncs.de</code> because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. ==active blocks== The live list of active blocks is [https://toot.cat/about/more here] (scroll down), but that doesn't give a history or any discussion of reasoning. The list here includes annotations and history, where available. * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 22ed55b0fcbe04448cebed8ca63e9a33a54070cf 228 227 2020-01-09T01:26:17Z Woozle 1 wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==change history== * '''[https://toot.cat/@news/103450367325621252 2020-01-08]''' <code>uwu.social</code> blocked (Facism, transmisia, hosting Gab users, etc) * '''2019-12-30''' After discussion with the admin team, we're removing silence from <code>social.tchncs.de</code> because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. ==active blocks== The live list of active blocks is [https://toot.cat/about/more here] (scroll down), but that doesn't give a history or any discussion of reasoning. The list here includes annotations and history, where available. * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 1cd5bbabd875d3909902a52e263f090662d7c95e 244 228 2020-07-22T17:41:59Z Woozle 1 much updating and record curation wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==new blocks== * '''[https://toot.cat/@news/103450367325621252 2020-01-08]''' <code>uwu.social</code> blocked (Facism, transmisia, hosting Gab users, etc) ==blocks rescinded== Mastodon apparently does not log a time-stamp or admin name for domain blocks. We therefore have to keep a manual log if we want that information recorded in a manageable way. * '''2020-07-22''' {{l/sub|inex.rocks}}: [https://toot.cat/admin/instances/inex.rocks block record] says only "defending fascism" * '''2020-07-13''' {{ls/domain|videos.lukesmith.xyz}} [https://toot.cat/@news/104508122890176142 probably Xenon]: "Fascism, slurs, etc." * '''2020-07-09''' [https://toot.cat/@news/104486195518238869 several blocks from Xenon]: ** {{ls/domain|boseburo.ddns.net}} From the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 Xenon]): {{ls/domain|witches.live}}: Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]) ** ([https://toot.cat/@news/104065944841866454 post]) * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]) ** ([https://toot.cat/@news/104016220466722385 post]) ** ([https://toot.cat/@news/104015379090184018 post]) * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): ** ([https://toot.cat/@news/103675388875266656 post]): * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): ** ([https://toot.cat/@news/103517317089844019 post]): * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): * '''2020-01-08''' ([https://toot.cat/@news/103466494343238412 post]) * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) ==legacy blocks== The live list of active blocks is [https://toot.cat/about/more here] (scroll down), but that doesn't give a history or any discussion of reasoning. The list here includes annotations and history, where available. * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} fe274ad423269fa734b017b03605f661e9dff049 245 244 2020-07-22T18:05:04Z Woozle 1 /* blocks rescinded */ oops, mixed in new blocks with rescinded... need to save in order to fix wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==new blocks== * '''[https://toot.cat/@news/103450367325621252 2020-01-08]''' <code>uwu.social</code> blocked (Facism, transmisia, hosting Gab users, etc) ==blocks rescinded== Mastodon apparently does not log a time-stamp or admin name for domain blocks. We therefore have to keep a manual log if we want that information recorded in a manageable way. * '''2020-07-22''' {{l/sub|inex.rocks}}: [https://toot.cat/admin/instances/inex.rocks block record] says only "defending fascism" * '''2020-07-13''' {{ls/domain|videos.lukesmith.xyz}} [https://toot.cat/@news/104508122890176142 probably Xenon]: "Fascism, slurs, etc." * '''2020-07-09''' [https://toot.cat/@news/104486195518238869 several blocks from Xenon]: ** {{ls/domain|boseburo.ddns.net}} From the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 Xenon]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/sub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]) * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): ** ([https://toot.cat/@news/103675388875266656 post]): * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): ** ([https://toot.cat/@news/103517317089844019 post]): * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): * '''2020-01-08''' ([https://toot.cat/@news/103466494343238412 post]) * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) ==legacy blocks== The live list of active blocks is [https://toot.cat/about/more here] (scroll down), but that doesn't give a history or any discussion of reasoning. The list here includes annotations and history, where available. * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 10101028cdb0bd9cc8f5188d7231d55edd0e8b08 246 245 2020-07-22T18:18:59Z Woozle 1 let's break this page up a bit... saving what I've got wikitext text/x-wiki ==policy== All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==new blocks== * '''2020-07-13''' {{ls/domain|videos.lukesmith.xyz}} [https://toot.cat/@news/104508122890176142 probably Xenon]: "Fascism, slurs, etc." * '''2020-07-09''' [https://toot.cat/@news/104486195518238869 several blocks from Xenon]: ** {{ls/domain|boseburo.ddns.net}} From the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 Xenon]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/sub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): ** ([https://toot.cat/@news/103517317089844019 post]): * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ==blocks rescinded== Mastodon apparently does not log a time-stamp or admin name for domain blocks. We therefore have to keep a manual log if we want that information recorded in a manageable way. * '''2020-07-22''' {{l/sub|inex.rocks}}: [https://toot.cat/admin/instances/inex.rocks block record] says only "defending fascism" * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) ==legacy blocks== The live list of active blocks is [https://toot.cat/about/more here] (scroll down), but that doesn't give a history or any discussion of reasoning. The list here includes annotations and history, where available. * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} f78b1fc877ee33986c1387f39cf5ccb338c50347 250 246 2020-07-22T18:36:07Z Woozle 1 moved long lists to subpages for easier editing wikitext text/x-wiki ==policy== The live list of active domain blocks is [https://toot.cat/about/more here] (scroll down) &ndash; but that doesn't give a history or any discussion of reasoning, nor does Mastodon appear to log a time-stamp or admin name for domain blocks. We therefore have to keep a manual log if we want that information recorded in a manageable way. ==pages== * [[/logged]]: blocks enacted since we started keeping records * [[/legacy]]: blocks enacted before that ==blocks rescinded== * '''2020-07-22''' {{l/sub|inex.rocks}}: [https://toot.cat/admin/instances/inex.rocks block record] says only "defending fascism" * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) 7289643db5dd5b0838321e97cbd221ad821a2979 254 250 2020-07-22T18:44:19Z Woozle 1 /* blocks rescinded */ wikitext text/x-wiki ==policy== The live list of active domain blocks is [https://toot.cat/about/more here] (scroll down) &ndash; but that doesn't give a history or any discussion of reasoning, nor does Mastodon appear to log a time-stamp or admin name for domain blocks. We therefore have to keep a manual log if we want that information recorded in a manageable way. ==pages== * [[/logged]]: blocks enacted since we started keeping records * [[/legacy]]: blocks enacted before that ==blocks rescinded== * '''2020-07-22''' {{l/pub|inex.rocks}} * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) 8d0ff03e029904401cf955ce1682d5d1cd7a9742 255 254 2020-07-22T18:46:04Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list]] to [[Pub/toot.cat/blocks/domain]]: more precise wikitext text/x-wiki ==policy== The live list of active domain blocks is [https://toot.cat/about/more here] (scroll down) &ndash; but that doesn't give a history or any discussion of reasoning, nor does Mastodon appear to log a time-stamp or admin name for domain blocks. We therefore have to keep a manual log if we want that information recorded in a manageable way. ==pages== * [[/logged]]: blocks enacted since we started keeping records * [[/legacy]]: blocks enacted before that ==blocks rescinded== * '''2020-07-22''' {{l/pub|inex.rocks}} * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) 8d0ff03e029904401cf955ce1682d5d1cd7a9742 0 62 211 2019-09-11T22:25:51Z Woozle 1 copied straight from admin settings (only change is to remove hr tags) wikitext text/x-wiki <h1>Code of Conduct</h1> <h2>General</h2> <p>As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users of the instance.</p> <p>We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.</p> <p>We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination.</p> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> <h2>Nudity / Sex / Kink (NSK)</h2> <h3>NSK Content Warnings</h3> <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> <h3>NSK Consent To Post</h3> <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (ie: prostitute, hooker, whore)</p> <h2>Closing</h2> <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> 8d7833d8782a39cf6dda9c376c815a2ade05a55c 217 211 2019-10-04T17:33:59Z Woozle 1 format tidying, minor correction wikitext text/x-wiki =Code of Conduct= ==General== <p>As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users of the instance.</p> <p>We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.</p> <p>We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination.</p> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> c26f814e97620e1f8129c388d44723ff0620df2c 218 217 2019-10-21T18:26:19Z Woozle 1 wikitext text/x-wiki =Code of Conduct= ==General== <p>As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users of the instance.</p> <p>We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.</p> <p>We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination.</p> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> 855bfe57830033fc33b50eee1485560322add0a7 235 218 2020-03-08T22:01:06Z Woozle 1 bots wikitext text/x-wiki =Code of Conduct= ==General== <p>As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users of the instance.</p> <p>We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.</p> <p>We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination.</p> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> 00bec0bbaf6908a3658c7accd3860a648ed93173 236 235 2020-03-28T00:12:32Z Woozle 1 commercial accounts wikitext text/x-wiki =Code of Conduct= ==General== <p>As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users of the instance.</p> <p>We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.</p> <p>We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination.</p> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Accounts== Accounts that appear to be oriented towards promoting a business will be suspended without warning unless we have previously granted permission. We do wish to support individuals and cooperatively-organized groups engaged in activities to support themselves and their communities, but we also want to understand your goals and methods &ndash; and we will want to have some pretty solid communication around that established first. We will not accept paid advertising. We are all part of the human community, and we reject the idea that possession of money entitles the holder to obligations by others. ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> 39e32363e2233a3b5951736d0c786c45d2744826 0 48 212 189 2019-09-11T22:28:29Z Woozle 1 CoC wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}. ==Information== * [[/block list]] * [[/CoC]]: Code of Conduct ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] af4d36c8261ceb471ff9a2ef661768392d0da4ad 219 212 2019-12-01T13:36:21Z Woozle 1 /* Links */ archive.org wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}. ==Information== * [[/block list]] * [[/CoC]]: Code of Conduct ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] 63cefc31f59b85376089b618e93a282fe65f4d41 223 219 2019-12-26T22:14:47Z Woozle 1 /* Information */ CoJ wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}. ==Information== * [[/block list]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] f45b6d39ace3dfd5646d2d98f3170db8d88393e3 233 223 2020-03-02T21:47:14Z Woozle 1 guidelines wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}. ==Information== * [[/block list]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] 776051e7385c47e76dae96ebd562c3ee83771eae 0 1 215 200 2019-09-18T14:58:23Z Woozle 1 /* Public Pages */ link to pub index page wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 0cc7102e244d2a4a3d82f3cce8da9f26dbfa2bc5 238 215 2020-03-31T23:42:48Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 294f578eb4c3f716084fdfc99e7821b08c9fe402 0 64 216 2019-09-18T15:02:03Z Woozle 1 Created page with "'''Gab''' is a build of Mastodon. It appears to have a reputation as being popular with {{l/ip|frozen fruit}} advocates. ==Links== * [https://fediverse.network/mastodon?build=..." wikitext text/x-wiki '''Gab''' is a build of Mastodon. It appears to have a reputation as being popular with {{l/ip|frozen fruit}} advocates. ==Links== * [https://fediverse.network/mastodon?build=gab instances using Gab] 323fcc642132b077cf1f194a6c07e54afd8377f5 0 42 220 192 2019-12-08T21:47:37Z Woozle 1 /* Non-Catal* .cat domains */ blob.cat wikitext text/x-wiki The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about {{l/pub|Catalonia}} as it comes our way. * We are interested in making space for content related to Catalonia and/or {{l/pub|Catalan}}. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|blob.cat}}: a [[Pleroma]] instance * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Mastodon user Sam Toland [https://social.coop/@samtoland/100152739177441119 notes] that the .cat admins used to be much stricter, but have now loosened enforcement a bit. 66246914f7a2b7e645933b44ed8df1fa478a5285 0 47 221 148 2019-12-08T22:21:28Z Woozle 1 domain change (should have fixd this ages ago) wikitext text/x-wiki Everything that was here has been moved to [https://wiki.florencesoc.org the Florence wiki]. 521b38f459ae6e1e371f142efba5e39c46441784 0 65 222 2019-12-26T22:14:40Z Woozle 1 Created page with "=The TootCat Code of Justice= {{box/principles| : Words have consequences. : All accusations should be taken seriously. }} ==License== This CoJ is basically an ''idea'', and a..." wikitext text/x-wiki =The TootCat Code of Justice= {{box/principles| : Words have consequences. : All accusations should be taken seriously. }} ==License== This CoJ is basically an ''idea'', and as such cannot be legally protected from re-use. In case there is any ambiguity, however, we release the text on this page into the public domain. Other instances may adopt this, modify it, or (it shouldn't need to be said) ignore it completely; I'm content to let the marketplace of kindness<ref name=note1 /> decide whether such a thing is necessary or not, and to let the process of considered discussion refine it as needed. {{box/principles| : No accusation should be accepted as truth unless the evidence supports it. : A lie often contains just enough truth to make it plausible. : Both accusers and accused may need some protection. }} ==Status== This proposal is being posted by Woozle (TootCat &uuml;berwensch) and has not yet been reviewed for acceptance by our admins or users. Prior agreement with these terms will not, unlike with a CoC, be required for usage of TC; I will just want to make sure that everyone is aware of the process we intend to follow in the event of a dispute. This draft of the proposal also leaves a lot of ground uncovered, and I hope to address at least some of that before publicizing it further. [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 22:14, 26 December 2019 (UTC) ==Public Intervention Process<ref name=pip />== '''If you have a grievance against another user'''<ref name=note2 /> and would like me (as sysop of this instance) to do something about it: # "@" me (@woozle@toot.cat) with a public<ref name=public /> toot stating the nature of the problem and that you are requesting an Intervention. #* The primary types of problem I expect to be addressing are: (a) someone has abused you, or (b) someone has falsely accused you of abuse &ndash; but others may emerge. # This means I have your permission to investigate the situation and publicly post my findings on Mew (this wiki). #* I will probably need to ask a lot of nosy questions, both to you and the other parties involved. Let me know if you anticipate any problems with this. #* These discussions should take place on Mastodon<ref name=mastodm /> so as to be part of the public record, though I can make exceptions if there's a good reason. # Once I have investigated sufficiently to satisfy ''my'' standards of evidence, I will post a preliminary determination for public feedback. # Anyone may state objections to this conclusion at any time, and I will either answer them or reconsider my conclusion, possibly re-opening the investigation. # Anyone may choose to go on record as supporting or opposing the conclusion. I will make these part of the public record to the best of my ability. #* Please note that opposition is not the same as stating an objection. I won't reconsider just because you oppose; you need to make an argument for why it is wrong. {{box/principles| : I strive to evaluate first in terms of potential harm. : I strive not to decide until I have all the relevant facts. }} Please note that this is a good-faith process &ndash; i.e. one that depends on all participants being honest about their beliefs and intentions &ndash; and I will deal firmly with anyone I find to be acting otherwise. I have over a decade of experience spotting manipulation and evasion in online arguments. ==Related Pages== This idea was originally discussed and proposed on these pages: * {{l/pub|user/woozle/2018/04/05/justice in the fediverse}}: philosophical foundation * {{l/pub|user/woozle/2018/04/07/sketching a code}}: first draft of the process ==Footnotes== <references> <ref name=note1>This is a reference to the semi-capitalistic "marketplace of ideas" concept, with an ironic twist since capitalists don't seem to place much (if any) value on kindness (so their marketplaces tend to squash it out of existence) and since most Mastodonians are staunchly anti-marketist. That said, the idea of having numerous instances among which users may freely choose to invest various amounts of their time and energy actually ''is'' a kind of marketplace that's totally compatible with anarcho-capitalism &ndash; except I think we'd all tend to agree that basically having one person who gets to decide pretty much everything about how the system works is kind of iffy.</ref> <ref name=note2>This applies whether or not either user is on toot.cat, though obviously my actions will be more effective if one or the other is.</ref> <ref name=public>You could also approach me privately (DM or whatever) to discuss it before stating it publicly, or you might need me to try to keep your name out of the public process. I'm willing to consider intervening less publicly, but I suspect it will severely limit any good I might be able to do; if this emerges as a frequent need, I'll probably need to write up a separate process for dealing with it.</ref> <ref name=pip>It seems entirely appropriate that this abbreviates to PIP, which is also the name of our very messed-up cat ([https://toot.cat/@Pip Mastodon], [https://wiki.hypertwins.org/Pip HypertWiki]), since it is only invoked when a situation has become very messed-up. It is my hope that this process will soon become informally known as "requesting a Pip".</ref> <ref name=mastodm>Tentatively, this should be public but "unlisted" or "followers only". I may need to set up a dedicated investigation account so people can decide whether they want the investigation in their streams or not.</ref> </references> 4a48d4fd850a96bc70dea9bab1089d400a872d4d 0 54 229 185 2020-01-12T01:54:33Z Woozle 1 wikitext text/x-wiki [[category:instances]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} * {{ls/domain|witches.live}} "a mastodon instance for witches" ** [https://fedi.lynnesbian.space/@lynnesbian/101883861030638834 2019-04-07]: problem with the admin? it sounds like partly a misunderstanding, though Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} 7b51cbb634a8a5f4d27f3927505ec83430966c88 0 44 230 186 2020-02-24T22:32:21Z Woozle 1 wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://lor.sh/@dump_stack dump_stack] | {{ls/domain|lor.sh}} | Mastodon | * '''2020-02-24''' [https://lor.sh/@dump_stack/103715838645490658] "people have anti-homeless attitudes because most of the time being homeless is a choice not a matter of chance." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li. '''Update 2018-10-07''': They have now been blocked after a report from a known user.</ref> </references> dad52bb7f102c4c2dc604ee3a18c5de4dcd55e3e 2 6 231 126 2020-02-24T22:32:48Z Woozle 1 wikitext text/x-wiki [[Pub/user/woozle|public page]] ==Projects== * [[ForkTogether]] (non-public stuff) ==Situations== * [[witches.town]] ==Dialogues== * [[/octodon.social/@Megan]] f179b2e09399c0b25fa83acc07e802dad673737e 0 66 232 2020-03-02T21:47:04Z Woozle 1 Created page with "==Red Flags== TootCat will block individuals and instances who persistently raise these flags: * '''Punching down''': it's not okay to punch down, and it's okay to call out pe..." wikitext text/x-wiki ==Red Flags== TootCat will block individuals and instances who persistently raise these flags: * '''Punching down''': it's not okay to punch down, and it's okay to call out people who are doing it. ** In general, "punching down" means criticizing people who are underprivileged or have less power than you. ** Examples: *** making fun of nontraditional pronouns [https://social.panthermodern.net/@0x00/103754842757342400] *** deliberately misgendering someone, especially a trans person * '''Using "free speech" as an excuse''' ({{l/ip|free speech trolling}}) ** {{l/ip|Freedom of speech}} just means ''the government'' can't stop you from saying things. ** It does not mean freedom from consequences if you say something obnoxious or hurtful. ** It does not mean that any private venue is required to give you a platform. 015e0d77a23fbdf6f0d7b3e2fd91f940e3efa9b8 234 232 2020-03-02T22:38:34Z Woozle 1 wikitext text/x-wiki ==Red Flags== TootCat will block individuals and instances who persistently raise these flags: * '''Punching down''': it's not okay to punch down, and it's okay to call out people who are doing it. ** In general, "punching down" means criticizing people who are underprivileged or have less power than you. ** Examples: *** making fun of nontraditional pronouns [https://social.panthermodern.net/@0x00/103754842757342400] *** deliberately misgendering someone, especially a trans person * '''Using "free speech" as an excuse''' ({{l/ip|free speech trolling}}) ** {{l/ip|Freedom of speech}} just means ''the government'' can't stop you from saying things. ** It does not mean freedom from consequences if you say something obnoxious or hurtful. ** It does not mean that any private venue is required to give you a platform. ** One opinion is ''not'' as good/valid as any other ''if one of them is harmful''. a76846c97692805cb7c04d6dfdee5201ffe78026 0 67 237 2020-03-31T23:42:41Z Woozle 1 Created page with "'''07:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes." wikitext text/x-wiki '''07:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. 8dc05085d154b59c93f41c63714d6722ea40af92 239 237 2020-03-31T23:54:36Z Woozle 1 wikitext text/x-wiki * '''07:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''07:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. 0c8d3159dd8ecf513da9ad15f71892decf76591a 240 239 2020-04-01T00:25:48Z Woozle 1 wikitext text/x-wiki * '''07:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''07:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''08:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. 86629cc91210f69ccfc9e70b1f3addff16261949 241 240 2020-04-01T00:36:27Z Woozle 1 wikitext text/x-wiki * '''19:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''19:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''20:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. * '''20:35''' Snapshot done; resizing. "Resizing can take up to 1 minute per GB of data used by your Droplet." We've got a mostly-full 80 GB drive to resize with, so about an hour. 62483d5795efe3e8b2ace634a69f70e9872ed4a1 242 241 2020-04-01T01:05:57Z Woozle 1 wikitext text/x-wiki * '''19:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''19:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''20:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. * '''20:35''' Snapshot done; resizing. "Resizing can take up to 1 minute per GB of data used by your Droplet." We've got a mostly-full 80 GB drive to resize with, so about an hour. * '''21:02''' [https://toot.cat/@woozle/103920629656934017 Back online!] 838715e897e4f98567b7f2eb3f514e33717afac4 0 68 243 2020-07-22T17:08:26Z Woozle 1 Created page with "==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them..." wikitext text/x-wiki ==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person): ===The negative=== The [https://toot.cat/@girl/104462394989007467 one lead I was able to get] on this domain said: * The main admin is known to follow people on domains that are often considered problematic, specifically [https://expired.mentality.rip/about expired.mentality.rip], [https://lor.sh/about/more" lor.sh], and the admin's own domain ([https://enigmatic.observer/about enigmatic.observer]). * The second admin is [https://udongein.xyz/naiji naiji@udongein.xyz], which is another often-blocked domain and a quick glance at that profile in early July apparently showed direct communications with users on {{ls/domain|neckbeard.xyz}}, freespeechextremist, kiwifarms, pl.smuglo.li and other frequently blocked domains. I don't know anything about neckbeard, but "free speech extremism" does tend to refer to a lot of very toxic forms of advocacy, and {{l/ip|kiwifarms}} is, from all reports, just plain evil. ===That said...=== Merely being willing to engage in dialogue with toxic people does not necessarily mean that one is toxic. I do not wish to promote a culture of fearing guilt-by-association. Additionally, I have no idea of the nature of the contact; was naiji interacting ''approvingly'' with those folks, or in an appropriately skeptical manner? Is it happening in a way that causes nastiness to populate the timeline, if I federate with it? Ultimately, I think that should be up to my userbase to decide -- and this time, if there are incidents, we will document them for future reference. At this point, due primarily to a lack of documentation of what incident(s) triggered the current block: I've reversed it (with this page as a log of my reasoning), and we will just watch carefully for any future issues with it. ==Footnotes== <references> <ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 DM reply] (private) to [https://enigmatic.observer/users/inex Inex Code]</ref> </references> 786e9c2be348cec99220d49917ee35cc7ab365df 252 243 2020-07-22T18:39:32Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list/inex.rocks]] to [[Pub/inex.rocks]] without leaving a redirect: more sensible location wikitext text/x-wiki ==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person): ===The negative=== The [https://toot.cat/@girl/104462394989007467 one lead I was able to get] on this domain said: * The main admin is known to follow people on domains that are often considered problematic, specifically [https://expired.mentality.rip/about expired.mentality.rip], [https://lor.sh/about/more" lor.sh], and the admin's own domain ([https://enigmatic.observer/about enigmatic.observer]). * The second admin is [https://udongein.xyz/naiji naiji@udongein.xyz], which is another often-blocked domain and a quick glance at that profile in early July apparently showed direct communications with users on {{ls/domain|neckbeard.xyz}}, freespeechextremist, kiwifarms, pl.smuglo.li and other frequently blocked domains. I don't know anything about neckbeard, but "free speech extremism" does tend to refer to a lot of very toxic forms of advocacy, and {{l/ip|kiwifarms}} is, from all reports, just plain evil. ===That said...=== Merely being willing to engage in dialogue with toxic people does not necessarily mean that one is toxic. I do not wish to promote a culture of fearing guilt-by-association. Additionally, I have no idea of the nature of the contact; was naiji interacting ''approvingly'' with those folks, or in an appropriately skeptical manner? Is it happening in a way that causes nastiness to populate the timeline, if I federate with it? Ultimately, I think that should be up to my userbase to decide -- and this time, if there are incidents, we will document them for future reference. At this point, due primarily to a lack of documentation of what incident(s) triggered the current block: I've reversed it (with this page as a log of my reasoning), and we will just watch carefully for any future issues with it. ==Footnotes== <references> <ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 DM reply] (private) to [https://enigmatic.observer/users/inex Inex Code]</ref> </references> 786e9c2be348cec99220d49917ee35cc7ab365df 0 69 247 2020-07-22T18:30:14Z Woozle 1 Created page with "* '''2020-07-13''' {{ls/domain|videos.lukesmith.xyz}} [https://toot.cat/@news/104508122890176142 probably Xenon]: "Fascism, slurs, etc." * '''2020-07-09''' [https://toot.cat/@..." wikitext text/x-wiki * '''2020-07-13''' {{ls/domain|videos.lukesmith.xyz}} [https://toot.cat/@news/104508122890176142 probably Xenon]: "Fascism, slurs, etc." * '''2020-07-09''' [https://toot.cat/@news/104486195518238869 several blocks from Xenon]: ** {{ls/domain|boseburo.ddns.net}} From the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 Xenon]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/sub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): ** ([https://toot.cat/@news/103517317089844019 post]): * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) 566fa44c635de4155b922352fa9f4fc24ea5033a 248 247 2020-07-22T18:35:12Z Woozle 1 wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==2020== * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/sub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): ** ([https://toot.cat/@news/103517317089844019 post]): * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) d549fd292041cfc02ae7bbe8eebdfbf7937055f3 253 248 2020-07-22T18:43:15Z Woozle 1 I *think* that's all of them... wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==2020== * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc 10a9d924fa7ae13a11243a07f885596a62b7121f 0 70 249 2020-07-22T18:35:45Z Woozle 1 Created page with "* '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773..." wikitext text/x-wiki * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 45f78f46dd6994267a5d6ccfbaac8e6489cb707a 257 249 2020-07-22T18:46:04Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list/legacy]] to [[Pub/toot.cat/blocks/domain/legacy]]: more precise wikitext text/x-wiki * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 45f78f46dd6994267a5d6ccfbaac8e6489cb707a 10 71 251 2020-07-22T18:38:52Z Woozle 1 Created page with "[[../{{{1}}}|{{{1}}}]]" wikitext text/x-wiki [[../{{{1}}}|{{{1}}}]] 59d1b57c0df88282f84b35831c2736fdf09b0e0b 0 72 256 2020-07-22T18:46:04Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list]] to [[Pub/toot.cat/blocks/domain]]: more precise wikitext text/x-wiki #REDIRECT [[Pub/toot.cat/blocks/domain]] ce845f5d6c4d27a1a1ea87295280a1647c54c774 0 73 258 2020-07-22T18:46:04Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list/legacy]] to [[Pub/toot.cat/blocks/domain/legacy]]: more precise wikitext text/x-wiki #REDIRECT [[Pub/toot.cat/blocks/domain/legacy]] ccf21e087f1438c9ed7281b4ba47eeabafe1aa43 0 69 259 253 2020-07-22T18:46:04Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list/logged]] to [[Pub/toot.cat/blocks/domain/logged]]: more precise wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==2020== * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc 10a9d924fa7ae13a11243a07f885596a62b7121f 270 259 2021-01-07T14:08:19Z Woozle 1 wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==2020== * '''2021-01-07''' Pieville (see [[:File:2021-01-07.screen.See what's happening - Pieville.png|this screenshot]]) * '''2021-01-06''' Liberdon, after discussion with user and a mod (also a [https://toot.cat/web/statuses/105504258670114486 poll]) * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc bc73201ce5709ae0fc87419722cf4e238f7e1d4e 278 270 2022-03-24T15:09:06Z Woozle 1 wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==2020== * '''2022-03-24''' [https://freeatlantis.com/about/more freeatlantis.com]: see [https://cwre.org/w/Woozle/2022/03/24 this CWRE post] * '''2021-01-07''' Pieville (see [[:File:2021-01-07.screen.See what's happening - Pieville.png|this screenshot]]) * '''2021-01-06''' Liberdon, after discussion with user and a mod (also a [https://toot.cat/web/statuses/105504258670114486 poll]) * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc fbbda5f79278aec025cfa3a7ae72a8ee7c9bb691 282 278 2022-04-29T19:38:29Z Woozle 1 wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ==2020== * '''2022-04-29''' [https://honkwerx.tech/wildgoose honkwerx.tech]: admin advocates anti-trans violence [https://honkwerx.tech/notice/AIx0k1iha00hAykXya][https://honkwerx.tech/notice/AIx0oxWYbi7DbvQAWu] ([[:File:2022-04-29 at 15-36-28.screen.wildgoose (@wildgoose@honkwerx.tech).png|screenshot]]) * '''2022-03-24''' [https://freeatlantis.com/about/more freeatlantis.com]: see [https://cwre.org/w/Woozle/2022/03/24 this CWRE post] * '''2021-01-07''' Pieville (see [[:File:2021-01-07.screen.See what's happening - Pieville.png|this screenshot]]) * '''2021-01-06''' Liberdon, after discussion with user and a mod (also a [https://toot.cat/web/statuses/105504258670114486 poll]) * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc efd6708e43cf1f27a3d5e5d70ce0523b9fe3ad9f 284 282 2022-05-06T14:57:58Z Woozle 1 /* 2020 */ wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ''see also the automated lists at https://toot.cat/about/more'' ==2022== * '''2022-05-06''' [https://shrike.club/about shrike.club]: death threat -- https://archive.ph/PetvA * '''2022-04-29''' [https://honkwerx.tech/wildgoose honkwerx.tech]: admin advocates anti-trans violence [https://honkwerx.tech/notice/AIx0k1iha00hAykXya][https://honkwerx.tech/notice/AIx0oxWYbi7DbvQAWu] ([[:File:2022-04-29 at 15-36-28.screen.wildgoose (@wildgoose@honkwerx.tech).png|screenshot]]) * '''2022-03-24''' [https://freeatlantis.com/about/more freeatlantis.com]: see [https://cwre.org/w/Woozle/2022/03/24 this CWRE post] ==2021== * '''2021-01-07''' Pieville (see [[:File:2021-01-07.screen.See what's happening - Pieville.png|this screenshot]]) * '''2021-01-06''' Liberdon, after discussion with user and a mod (also a [https://toot.cat/web/statuses/105504258670114486 poll]) ==2020== * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc 9b928843d8fcbd33bbd435919b15689e76045065 0 74 260 2020-07-22T18:46:04Z Woozle 1 Woozle moved page [[Pub/toot.cat/block list/logged]] to [[Pub/toot.cat/blocks/domain/logged]]: more precise wikitext text/x-wiki #REDIRECT [[Pub/toot.cat/blocks/domain/logged]] 270ab2c3f810bdf2fcb254b48bbaf55497f1fd06 0 48 261 233 2020-07-22T18:46:48Z Woozle 1 /* Information */ updated internal link wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. @LottieVixen joined the admin team sometime in the next few weeks, and did excellent work migrating (from the original server image set up by the founding team) to a new system. @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ea0cdb259e84d8711e08c44d230e844b74be82db 272 261 2021-01-11T14:19:33Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ({{lpub/user|woozle}}) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Old Gnus== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) 4ca384dd423f878fdf0424ab211506c8b7a9de91 0 68 262 252 2020-07-23T00:35:23Z Woozle 1 /* Footnotes */ I actually posted it semi-public, which is sort of what I intended wikitext text/x-wiki ==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person): ===The negative=== The [https://toot.cat/@girl/104462394989007467 one lead I was able to get] on this domain said: * The main admin is known to follow people on domains that are often considered problematic, specifically [https://expired.mentality.rip/about expired.mentality.rip], [https://lor.sh/about/more" lor.sh], and the admin's own domain ([https://enigmatic.observer/about enigmatic.observer]). * The second admin is [https://udongein.xyz/naiji naiji@udongein.xyz], which is another often-blocked domain and a quick glance at that profile in early July apparently showed direct communications with users on {{ls/domain|neckbeard.xyz}}, freespeechextremist, kiwifarms, pl.smuglo.li and other frequently blocked domains. I don't know anything about neckbeard, but "free speech extremism" does tend to refer to a lot of very toxic forms of advocacy, and {{l/ip|kiwifarms}} is, from all reports, just plain evil. ===That said...=== Merely being willing to engage in dialogue with toxic people does not necessarily mean that one is toxic. I do not wish to promote a culture of fearing guilt-by-association. Additionally, I have no idea of the nature of the contact; was naiji interacting ''approvingly'' with those folks, or in an appropriately skeptical manner? Is it happening in a way that causes nastiness to populate the timeline, if I federate with it? Ultimately, I think that should be up to my userbase to decide -- and this time, if there are incidents, we will document them for future reference. At this point, due primarily to a lack of documentation of what incident(s) triggered the current block: I've reversed it (with this page as a log of my reasoning), and we will just watch carefully for any future issues with it. ==Footnotes== <references> <ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 reply] to [https://enigmatic.observer/users/inex Inex Code]</ref> </references> bc45d83ddfee7e08561f8f0185a5df75368a4fe1 0 75 263 2020-08-13T00:06:45Z Woozle 1 Created page with "[[category:instances]] See [[issuepedia:social.targaryen.house]] -- should probably move that page here." wikitext text/x-wiki [[category:instances]] See [[issuepedia:social.targaryen.house]] -- should probably move that page here. a316adece2c27332b106699a752c1a4c9fbccc80 12 27 264 68 2020-08-17T16:14:18Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Charlotte''': ** [https://liberapay.com/LottieVixen/ LiberaPay] ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] * '''Woozle''' (prim: ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running You can also mail checks to: : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 ==Resources== We need to maintain a wish-list... 2b24d5df02b4e7512f979115889b655d9714fd91 265 264 2020-08-21T14:19:30Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Charlotte''': ** [https://liberapay.com/LottieVixen/ LiberaPay] ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running You can also mail checks to: : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 ==Resources== We need to maintain a wish-list... 59950e69e8cf127c0c5c2783ba065e14d958a81a 273 265 2021-03-21T15:48:00Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''Team accounts''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** BitCoin available, but I need to make sure my wallet is running You can also mail checks to: : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 ==Resources== We need to maintain a wish-list... fb5592ca4ac815c54d1f1660ddf6fa4bfa5a8432 295 273 2022-10-30T17:00:35Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat's activities, there are several ways: ==Money== * '''TootCat''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] You can also mail checks to: : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 <!-- ==Resources== We need to maintain a wish-list... * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) --> 46ff116a85fab6710d514f8e2cf5fa68990b7e73 296 295 2022-11-07T14:10:31Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat, there are several ways: <!-- ==Money== --> * '''TootCat''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] You can also mail checks to: : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 <!-- ==Resources== We need to maintain a wish-list... * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) --> 17eb59ab2bc0e44f4c03659030547242050b79f3 6 76 268 2021-01-07T14:04:01Z Woozle 1 [[category:screenshot]] * '''what''': screenshot of [https://pieville.net Pieville]'s public home timeline * '''taken''': 2021-01-07 08:59 wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': screenshot of [https://pieville.net Pieville]'s public home timeline * '''taken''': 2021-01-07 08:59 73cd17c9298cdb9c5798898f373339744a7172a4 0 55 269 255 2021-01-07T14:05:12Z Woozle 1 wikitext text/x-wiki [[File:2021-01-07.screen.See what's happening - Pieville.png|thumb|why we blocked Pieville]] ==policy== The live list of active domain blocks is [https://toot.cat/about/more here] (scroll down) &ndash; but until recently, that didn't give a history or any discussion of reasoning, nor does Mastodon appear to log a time-stamp or admin name for domain blocks. Even now, it doesn't allow uploading of media or provide a way to allow more extensive discussion. We therefore have to keep a manual log if we want that information recorded in a manageable way. ==pages== * [[/logged]]: blocks enacted since we started keeping records * [[/legacy]]: blocks enacted before that ==blocks rescinded== * '''2020-07-22''' {{l/pub|inex.rocks}} * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) 75965e82f523ad7ba45a1bad200d8b51e318f581 0 66 271 234 2021-01-11T14:08:25Z Woozle 1 wikitext text/x-wiki ==Red Flags== TootCat will block individuals and instances who persistently raise these flags: * '''Punching down''': it's not okay to punch down, and it's okay to call out people who are doing it. ** In general, "punching down" means criticizing people who are underprivileged or have less power than you. ** Examples: *** making fun of nontraditional pronouns [https://social.panthermodern.net/@0x00/103754842757342400] *** deliberately misgendering someone, especially a trans person * '''Using "free speech" as an excuse''' ({{l/ip|free speech trolling}}) ** {{l/ip|Freedom of speech}} just means ''the government'' can't stop you from saying things. ** It does not mean freedom from consequences if you say something obnoxious or hurtful. ** It does not mean that any private venue is required to give you a platform. ** One opinion is ''not'' as good/valid as any other ''if one of them is harmful''. *** Inaccuracy of factual details is often (but not always) a cause of harm, as it can lead to maltreatment of others. [[issuepedia:Truth/evidenced|Truth]] matters. 2f453a26e1dbc4627e0241058d770ed2869d54eb 0 77 274 2021-10-27T13:53:59Z Woozle 1 Created page with "If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes HotMail, Outlook.com, and even some u..." wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes HotMail, Outlook.com, and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available; if you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. 742b2c9c1a117cfec1caf273a9671a92d685ec68 277 274 2021-10-27T14:05:57Z Woozle 1 wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes HotMail, Outlook.com, and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available; if you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' 7fb37d704092362911d3b0b190e4fd92b5326063 279 277 2022-04-28T14:38:01Z Woozle 1 wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes HotMail, Outlook.com, and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available; if you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' ==Related== * '''2022-04-28''' [https://toot.cat/@woozle/108210129980886571 I need to figure out what to do about people signing up for #TootCat (with) #Microsoft email addresses...] 2509b305d8972ca2f131858e1d310169819a208b 280 279 2022-04-28T14:43:04Z Woozle 1 wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes HotMail, Outlook.com, and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available; if you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' ==Related== * '''2022-04-28''' @woozle: [https://toot.cat/@woozle/108210129980886571 I need to figure out what to do about people signing up for #TootCat (with) #Microsoft email addresses...] * '''2021-10-27''' @woozle: [https://toot.cat/@woozle/107173957644432715 ... I need to put in a link to our new warning about Microsoft's email servers being chronically rude to me. ...] 8a4e4c55f7ec2d1bf50398930d8894bce9df7193 283 280 2022-05-06T14:40:17Z Woozle 1 wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes HotMail, Outlook.com, and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available; if you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' ==Related== * '''2022-05-06''' @woozle: [https://toot.cat/@woozle/108255493723637622 GMail has suddenly started bouncing our emails...]: I haven't confirmed whether toot.cat's emails are affected, but GMail is definitely blocking messages sent from one of our other servers (both are on DigitalOcean), so it seems likely. * '''2022-04-28''' @woozle: [https://toot.cat/@woozle/108210129980886571 I need to figure out what to do about people signing up for #TootCat (with) #Microsoft email addresses...] * '''2021-10-27''' @woozle: [https://toot.cat/@woozle/107173957644432715 ... I need to put in a link to our new warning about Microsoft's email servers being chronically rude to me. ...] 840b6ea0906cc5e1b015af1144eea4f079296781 285 283 2022-05-07T11:51:30Z Woozle 1 wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes '''HotMail''', '''Outlook.com''', and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available (and, lately, seems to be basically impossible); if you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' ==Related== * '''2022-05-06''' @woozle: [https://toot.cat/@woozle/108255493723637622 GMail has suddenly started bouncing our emails...]: I haven't confirmed whether toot.cat's emails are affected, but GMail is definitely blocking messages sent from one of our other servers (both are on DigitalOcean), so it seems likely. *** '''2022-05-07''' UPDATE: No, it was just cloud1. The error message from Google was ''completely'' misleading; the problem was that the server had been redlisted by Spamhaus, and I was able to get it de-listed. (No reason was given for why it got redlisted.) * '''2022-04-28''' @woozle: [https://toot.cat/@woozle/108210129980886571 I need to figure out what to do about people signing up for #TootCat (with) #Microsoft email addresses...] * '''2021-10-27''' @woozle: [https://toot.cat/@woozle/107173957644432715 ... I need to put in a link to our new warning about Microsoft's email servers being chronically rude to me. ...] 1c671bc07497869a5c10f2a25a8a395da8fabe76 286 285 2022-05-09T23:51:12Z Woozle 1 wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes '''HotMail''', '''Outlook.com''', and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available &ndash; and, lately, seems to be basically impossible: [https://answers.microsoft.com/en-us/outlook_com/forum/all/hotmailoutlook-block-list-s3140-blocks-all-new/699f3a56-406e-4804-97e2-cbe23b9bb01c this appears to be a Microsoft problem, not a technical issue on our end]. If you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' ==Related== * '''2022-05-06''' @woozle: [https://toot.cat/@woozle/108255493723637622 GMail has suddenly started bouncing our emails...]: I haven't confirmed whether toot.cat's emails are affected, but GMail is definitely blocking messages sent from one of our other servers (both are on DigitalOcean), so it seems likely. *** '''2022-05-07''' UPDATE: No, it was just cloud1. The error message from Google was ''completely'' misleading; the problem was that the server had been redlisted by Spamhaus, and I was able to get it de-listed. (No reason was given for why it got redlisted.) * '''2022-04-28''' @woozle: [https://toot.cat/@woozle/108210129980886571 I need to figure out what to do about people signing up for #TootCat (with) #Microsoft email addresses...] * '''2021-10-27''' @woozle: [https://toot.cat/@woozle/107173957644432715 ... I need to put in a link to our new warning about Microsoft's email servers being chronically rude to me. ...] f6da0aaba8ad07154e68575ec4911683a9a8f2d4 8 2 275 54 2021-10-27T13:56:06Z Woozle 1 wikitext text/x-wiki * navigation ** mainpage | wiki main page ** https://toot.cat | Toot Cat home ** recentchanges-url | recentchanges ** randompage-url | randompage ** Help:Contribute | Tip jar ** Help:Main | User help * SEARCH * TOOLBOX * LANGUAGES 3e4d4809116042decf18df4f93402e3aa1e779d9 276 275 2021-10-27T13:56:37Z Woozle 1 wikitext text/x-wiki * navigation ** mainpage | Wiki main page ** https://toot.cat | Toot.Cat home ** recentchanges-url | recentchanges ** randompage-url | randompage ** Help:Contribute | Tip jar ** Help:Main | User help * SEARCH * TOOLBOX * LANGUAGES bb5b6b0d08c6812a2d9d01e4c858dad32afb41a6 6 78 281 2022-04-29T19:37:45Z Woozle 1 [[category:screenshot]] [[category:violent]] [[category:transmisia]] wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:violent]] [[category:transmisia]] 67ce7d3e78ba3bf0d73882faf803ea855634b635 10 80 288 2022-05-24T00:16:14Z Woozle 1 Created page with "<div style="background: #ff7; border: 2px solid #080; width: 100%; padding: 5px;"> <span style="font: 18pt/16pt Times, serif">{{{1}}}</span> <br><span style="font: 12pt Times,..." wikitext text/x-wiki <div style="background: #ff7; border: 2px solid #080; width: 100%; padding: 5px;"> <span style="font: 18pt/16pt Times, serif">{{{1}}}</span> <br><span style="font: 12pt Times, serif">{{{2|}}}</span> </div> 79cc2db9abd8052f8c5eb8cc949239afc1f548a4 290 288 2022-05-24T00:38:56Z Woozle 1 wikitext text/x-wiki <div style="background: {{{color|#ff7}}}; border: 2px solid #080; width: 100%; padding: 5px;"> <span style="font: 18pt/16pt Times, serif">{{{1}}}</span> <br><span style="font: 12pt Times, serif">{{{2|}}}</span> </div> 3dcbe04df172c8846eac8002a6bceab3585033de 0 1 289 238 2022-05-24T00:19:29Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{hdr/notice|'''2022-05-23 20:18 EDT''' toot.cat is temporarily down for a system migration.|We're not having any actual problems; the data import is just taking rather longer than expected. We apologize for the indexision.}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 0418dfd32a64ad08e2a797f458122e4c101118dc 291 289 2022-05-24T00:40:17Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{hdr/notice|'''2022-05-23 20:37 EDT''' toot.cat is running ok.|Still doing a bit of cleanup, but basically everything looks good.|color=#8f4}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 06ef15e149f39b78b1c3d6005b04340710b6a323 292 291 2022-05-24T00:46:04Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{hdr/notice|'''2022-05-23 20:37 EDT''' toot.cat is running ok.|Still doing a bit of cleanup, but basically everything looks good. <small>...except for avatars and emoji. Those aren't looking good yet.</small>|color=#8f4}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> bed0248791fe38f16fe64c719b03fe827174cfe2 293 292 2022-05-24T00:57:21Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{hdr/notice|'''2022-05-23 20:56 EDT''' toot.cat is running ok.|Still doing a bit of cleanup from the migration, but basically everything looks good.|color=#8f4}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> f5336591b7af95efd9a600975a8cf9d15154ed71 294 293 2022-05-24T20:30:47Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{hdr/notice|'''2022-05-24 16:30 EDT''' toot.cat is running ok.|There are currently no known issues.|color=#8f4}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 6cb31ead0568d7571ba951914e3b4658e266d26d 300 294 2022-11-08T21:21:58Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{hdr/notice/warn|'''2022-11-08 16:30 EDT''' toot.cat is being slow and cranky.|Uploads work only sometimes, and it's slowly getting behind on messages during the busy part of the day.}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> db0afc2bf00f2dfcfcb557450b8a0142f1f6da23 309 300 2022-11-08T22:19:33Z Woozle 1 wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{i/val|status|page=toot.cat}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==Public Pages== * [[Pub]]: index * [[Mew:About]]: what this wiki is about ** {{l/pub|.cat}}: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/pub|cat}}: cat-related things ** {{l/cat|Instances}} (private namespace, logged-in users only) *** {{l/pub|witches}}: witchy instances * {{l/pub|user/woozle}}: Woozle's public pages ** {{l/pub|user/woozle/malusers}}: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> d9f0998729a53b167253382698b01b883129faee 10 81 297 2022-11-08T21:14:10Z Woozle 1 Created page with "{{hdr/notice|{{{1}}}|color=#8f4}}" wikitext text/x-wiki {{hdr/notice|{{{1}}}|color=#8f4}} 9f73addf43f2230086e098608ab3e1bda4a094ad 302 297 2022-11-08T21:25:11Z Woozle 1 wikitext text/x-wiki {{hdr/notice|{{{1}}}|{{{2|There are no known issues.}}}|color=#8f4}} 6e71fa9cf76336d9f47ed0d3b743c19b1d1b37ba 10 82 298 2022-11-08T21:14:44Z Woozle 1 Created page with "{{hdr/notice|{{{1}}}|color=#ff4}}" wikitext text/x-wiki {{hdr/notice|{{{1}}}|color=#ff4}} 4619dbd9d8c23f6880b7e634a1430ecf1e955946 299 298 2022-11-08T21:21:02Z Woozle 1 wikitext text/x-wiki {{hdr/notice|{{{1}}}|{{{2|}}}|color=#ff4}} 4d23fb5fa33d6283d8ec50cbfce8747a92202110 0 83 301 2022-11-08T21:23:49Z Woozle 1 Created page with "This is a test." wikitext text/x-wiki This is a test. afa6c8b3a2fae95785dc7d9685a57835d703ac88 8 84 303 2022-11-08T21:58:37Z Woozle 1 Created page with "* Common delete reasons ** Author request ** Broken redirect ** Copyright violation ** No longer needed ** Spam ** Vandalism" wikitext text/x-wiki * Common delete reasons ** Author request ** Broken redirect ** Copyright violation ** No longer needed ** Spam ** Vandalism 90b655fe10e3a2e03b97b303366c1aa7283206d9 10 85 304 2022-11-08T22:08:41Z Woozle 1 Created page with "<includeonly>[[category:{{#sub:{{{1|{{PAGENAME}}}}}|0|4}}/{{#sub:{{{1|{{PAGENAME}}}}}|5|2}}/{{#sub:{{{1|{{PAGENAME}}}}}|8|2}}]]category:{{#sub:{{{1|{{PAGENAME}}}}}|0|4}}/{{#..." wikitext text/x-wiki <includeonly>[[category:{{#sub:{{{1|{{PAGENAME}}}}}|0|4}}/{{#sub:{{{1|{{PAGENAME}}}}}|5|2}}/{{#sub:{{{1|{{PAGENAME}}}}}|8|2}}]][[category:{{#sub:{{{1|{{PAGENAME}}}}}|0|4}}/{{#sub:{{{1|{{PAGENAME}}}}}|5|2}}]][[category:{{#sub:{{{1|{{PAGENAME}}}}}|0|4}}]][[category:dates/{{#sub:{{{1|{{PAGENAME}}}}}|5|2}}/{{#sub:{{{1|{{PAGENAME}}}}}|8|2}}]]</includeonly> bbbb9cc44afa858bba04fce0f415af9dd6655a15 10 86 305 2022-11-08T22:11:46Z Woozle 1 Created page with "<div style="background: {{{color|#efb}}}; border: 2px solid #080; width: 100%; padding: 5px;"> <span style="font: 18pt/16pt Times, serif">{{{1}}}</span> <br><span style="font:..." wikitext text/x-wiki <div style="background: {{{color|#efb}}}; border: 2px solid #080; width: 100%; padding: 5px;"> <span style="font: 18pt/16pt Times, serif">{{{1}}}</span> <br><span style="font: 12pt Times, serif">{{{2|}}}</span> </div> e63dc72128580c8d937de6f930c3eba5506924ff 10 87 306 2022-11-08T22:11:57Z Woozle 1 Created page with "{{c/date|{{PAGENAME}}}} [[category:time]] [[category:date]] {{fmt/title| {{#time: l, F j, Y | {{PAGENAME}}}} {{#time: (#z) | {{PAGENAME}} + 1 day}} }} <table width=100% style..." wikitext text/x-wiki {{c/date|{{PAGENAME}}}} [[category:time]] [[category:date]] {{fmt/title| {{#time: l, F j, Y | {{PAGENAME}}}} {{#time: (#z) | {{PAGENAME}} + 1 day}} }} <table width=100% style="border-bottom: 1px solid green;"><tr><td valign=bottom> <table class=wikitable><tr> <td> [[ {{#time: Y/m/d | {{PAGENAME}} - 1 day}} | {{#time: l | {{PAGENAME}} - 1 day}} ]] </td> <td> '''{{#time: l | {{PAGENAME}}}}''' </td> <td> [[ {{#time: Y/m/d | {{PAGENAME}} + 1 day}} | {{#time: l | {{PAGENAME}} + 1 day}} ]] </td> </tr></table> 6198710a7e398646b220e454c0ebb726bcb68319 10 88 307 2022-11-08T22:16:45Z Woozle 1 Created page with "<includeonly>{{#ifexist: {{{page|{{FULLPAGENAME}}}}}/var/${{{1}}} | {{:{{{page|{{FULLPAGENAME}}}}}/var/${{{1}}}}} | {{{2|{{{page|{{FULLPAGENAME}}}}}/var/${{{1}}}|[add {{{1}}..." wikitext text/x-wiki <includeonly>{{#ifexist: {{{page|{{FULLPAGENAME}}}}}/var/${{{1}}} | {{:{{{page|{{FULLPAGENAME}}}}}/var/${{{1}}}}} | {{{2|[[{{{page|{{FULLPAGENAME}}}}}/var/${{{1}}}|[add {{{1}}}]]]}}} }}</includeonly> a557b2bc9f20d3900bd5c6eb1605cac65fb259f1 0 89 308 2022-11-08T22:18:56Z Woozle 1 Created page with "{{hdr/notice/warn|'''2022-11-08 16:30 EDT''' toot.cat is being slow and cranky.|Uploads work only sometimes, and it's slowly getting behind on messages during the busy part of..." wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-08 16:30 EDT''' toot.cat is being slow and cranky.|Uploads work only sometimes, and it's slowly getting behind on messages during the busy part of the day.}} 3e125129bfd9af1ac2728c68e0f6f18516959510 10 90 310 2022-11-09T00:49:40Z Woozle 1 Created page with "[[wikipedia:{{{1}}}|{{{2|{{{1}}}}}}]]" wikitext text/x-wiki [[wikipedia:{{{1}}}|{{{2|{{{1}}}}}}]] b9599977df9e5a35be670729675789567f7ca2fd 0 83 311 301 2022-11-09T00:50:03Z Woozle 1 wikitext text/x-wiki {{page/date}} {{i/val|status|page=toot.cat}} Today has been a mess of interruptions so I didn't get much chance to work on the issues, but here's a quick summary of where we are: * images sometimes will upload, but sometimes take effectively forever * This ''may'' be due to needing an upgrade; see [https://toot.cat/@clarfonthey/109310137891163841 clar fon's post]. * Doing a site upgrade was already high on my priority queue; it's now the main thing. * The obstacle, however, is that the failsafe upgrade script set up for me by ghost!admin isn't working. * That script is written in {{l/wp|Nix (package manager)|Nix}} (the entire site is now running under {{L/wp|NixOS}}), so in order to debug it I need to understand a bit more about Nix. ==The Nix Issue== The first step in the upgrade is to start Nix on my desktop -- but I get an error when I do that: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override My recollection is that I tried the <code>--extra-experimental-features</code> option the last time I ran into this (several months ago), and that led to another dead-end -- but I suppose I could try it again and document that. For now, however, this is where I am stuck. cd2cb6fe992748247df2465d20cce8762a3edf5c 313 311 2022-11-09T01:07:09Z Woozle 1 wikitext text/x-wiki {{page/date}} {{i/val|status|page=toot.cat}} Today has been a mess of interruptions so I didn't get much chance to work on the issues, but here's a quick summary of where we are: * images sometimes will upload, but sometimes take effectively forever * This ''may'' be due to needing an upgrade; see [https://toot.cat/@clarfonthey/109310137891163841 clar fon's post]. * Doing a site upgrade was already high on my priority queue; it's now the main thing. * The obstacle, however, is that the failsafe upgrade script set up for me by ghost!admin isn't working. * That script is written in {{l/wp|Nix (package manager)|Nix}} (the entire site is now running under {{L/wp|NixOS}}), so in order to debug it I need to understand a bit more about Nix. ==The Nix Issue== The first step in the upgrade is to start Nix on my desktop -- but I get an error when I do that: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override My recollection is that I tried the <code>--extra-experimental-features</code> option the last time I ran into this (several months ago), and that led to another dead-end -- but I suppose I could try it again and document that. For now, however, this is where I am stuck. ==Funds== * The server ''was'' costing $48/mo (DigitalOcean). * Last night, I doubled the CPU and RAM (to 8vCPUs, 16 GB RAM); we're now burning $96/mo, as long as I keep it at that level. ** It's not actually clear how much it helped. I'll have more data to look at after a day or two. The queue was getting longer all this afternoon, after having gotten almost cleared this morning. * I'm not sure exactly what the current revenue is. ** A lot of new donations came in over the past week; I'm not sure what portion were one-time. ** Prior to this week, monthly revenue was somewhere around $80-110. If that keeps up, then we go from "having a little extra for personal support" to "maybe breaking even". ** I... should probably talk about my [family's/personal] financial situation at some point, but that gets complicated. TLDR: overworked, underfunded, unemployed. * Yes, I do plan to do some fundraising -- but I kind of want to [https://toot.cat/@woozle/109310543266479370 fix things first]. 2a8100f01ea2abebb3bdaba079ed7586f289db37 315 313 2022-11-09T01:59:33Z Woozle 1 /* The Nix Issue */ wikitext text/x-wiki {{page/date}} {{i/val|status|page=toot.cat}} Today has been a mess of interruptions so I didn't get much chance to work on the issues, but here's a quick summary of where we are: * images sometimes will upload, but sometimes take effectively forever * This ''may'' be due to needing an upgrade; see [https://toot.cat/@clarfonthey/109310137891163841 clar fon's post]. * Doing a site upgrade was already high on my priority queue; it's now the main thing. * The obstacle, however, is that the failsafe upgrade script set up for me by ghost!admin isn't working. * That script is written in {{l/wp|Nix (package manager)|Nix}} (the entire site is now running under {{L/wp|NixOS}}), so in order to debug it I need to understand a bit more about Nix. ==The Nix Issue== The first step in the upgrade is to start Nix on my desktop -- but I get an error when I do that: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override My recollection is that I tried the <code>--extra-experimental-features</code> option the last time I ran into this (several months ago), and that led to another dead-end -- but I suppose I could try it again and document that. Yeah, here we go: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features develop warning: unknown experimental feature 'develop' error: no subcommand specified Try 'nix --help' for more information. Am I understanding the error message correctly? Maybe it meant... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied I don't know if that's better or worse. Anyway, that's where I'm stuck now. ==Funds== * The server ''was'' costing $48/mo (DigitalOcean). * Last night, I doubled the CPU and RAM (to 8vCPUs, 16 GB RAM); we're now burning $96/mo, as long as I keep it at that level. ** It's not actually clear how much it helped. I'll have more data to look at after a day or two. The queue was getting longer all this afternoon, after having gotten almost cleared this morning. * I'm not sure exactly what the current revenue is. ** A lot of new donations came in over the past week; I'm not sure what portion were one-time. ** Prior to this week, monthly revenue was somewhere around $80-110. If that keeps up, then we go from "having a little extra for personal support" to "maybe breaking even". ** I... should probably talk about my [family's/personal] financial situation at some point, but that gets complicated. TLDR: overworked, underfunded, unemployed. * Yes, I do plan to do some fundraising -- but I kind of want to [https://toot.cat/@woozle/109310543266479370 fix things first]. 4e69ab3fce3d35afb243949b48c1d6265f7ec5a4 317 315 2022-11-09T02:06:40Z Woozle 1 wikitext text/x-wiki {{page/date}} {{i/val|status|page=toot.cat}} Today has been a mess of interruptions so I didn't get much chance to work on the issues, but here's a quick summary of where we are: * images sometimes will upload, but sometimes take effectively forever * This ''may'' be due to needing an upgrade; see [https://toot.cat/@clarfonthey/109310137891163841 clar fon's post]. * Doing a site upgrade was already high on my priority queue; it's now the main thing. * The obstacle, however, is that the failsafe upgrade script set up for me by ghost!admin isn't working. * That script is written in {{l/wp|Nix (package manager)|Nix}} (the entire site is now running under {{L/wp|NixOS}}), so in order to debug it I need to understand a bit more about Nix. I put the tech stuff in a subpage: [[/Nix issue]] ==Funds== * The server ''was'' costing $48/mo (DigitalOcean). * Last night, I doubled the CPU and RAM (to 8vCPUs, 16 GB RAM); we're now burning $96/mo, as long as I keep it at that level. ** It's not actually clear how much it helped. I'll have more data to look at after a day or two. The queue was getting longer all this afternoon, after having gotten almost cleared this morning. * I'm not sure exactly what the current revenue is. ** A lot of new donations came in over the past week; I'm not sure what portion were one-time. ** Prior to this week, monthly revenue was somewhere around $80-110. If that keeps up, then we go from "having a little extra for personal support" to "maybe breaking even". ** I... should probably talk about my [family's/personal] financial situation at some point, but that gets complicated. TLDR: overworked, underfunded, unemployed. * Yes, I do plan to do some fundraising -- but I kind of want to [https://toot.cat/@woozle/109310543266479370 fix things first]. 96a29d17688bc6b38e1ee077628ce79e89e93089 320 317 2022-11-09T13:24:43Z Woozle 1 wikitext text/x-wiki {{page/date}} Today has been a mess of interruptions so I didn't get much chance to work on the issues, but here's a quick summary of where we are: * images sometimes will upload, but sometimes take effectively forever * This ''may'' be due to needing an upgrade; see [https://toot.cat/@clarfonthey/109310137891163841 clar fon's post]. * Doing a site upgrade was already high on my priority queue; it's now the main thing. * The obstacle, however, is that the failsafe upgrade script set up for me by ghost!admin isn't working. * That script is written in {{l/wp|Nix (package manager)|Nix}} (the entire site is now running under {{L/wp|NixOS}}), so in order to debug it I need to understand a bit more about Nix. I put the tech stuff in a subpage: [[/Nix issue]] ==Funds== * The server ''was'' costing $48/mo (DigitalOcean). * Last night, I doubled the CPU and RAM (to 8vCPUs, 16 GB RAM); we're now burning $96/mo, as long as I keep it at that level. ** It's not actually clear how much it helped. I'll have more data to look at after a day or two. The queue was getting longer all this afternoon, after having gotten almost cleared this morning. * I'm not sure exactly what the current revenue is. ** A lot of new donations came in over the past week; I'm not sure what portion were one-time. ** Prior to this week, monthly revenue was somewhere around $80-110. If that keeps up, then we go from "having a little extra for personal support" to "maybe breaking even". ** I... should probably talk about my [family's/personal] financial situation at some point, but that gets complicated. TLDR: overworked, underfunded, unemployed. * Yes, I do plan to do some fundraising -- but I kind of want to [https://toot.cat/@woozle/109310543266479370 fix things first]. 202a41e606390251c97cebeefc0c9ac33156a605 8 91 312 2022-11-09T00:55:49Z Woozle 1 Created page with "/* CSS placed here will be applied to all skins */ /* make links stand out more */ a { border-bottom: dashed 1px grey; text-shadow: -2px 2px 2px #CCC; } /* hidden text */..." css text/css /* CSS placed here will be applied to all skins */ /* make links stand out more */ a { border-bottom: dashed 1px grey; text-shadow: -2px 2px 2px #CCC; } /* hidden text */ .secret { color: #888; background: #888; } .secret:hover { color: black; background: #eee; } f4206a180e649286a8038e38eb4b20545e068436 2 6 314 231 2022-11-09T01:15:10Z Woozle 1 wikitext text/x-wiki Me: * [https://toot.cat/@woozle toot.cat], of course * [https://woozalia.com creative stuff] * [https://wooz.dev software stuff] * [https://hypertwins.org family stuff] I also run [https://issuepedia.org Issuepedia], [https://htyp.org HTYP], and a few other specialty sites. ...and I host creative sites for two friends: * [https://outside-life.com Outside Life], a webcomic by drazahoib * [https://roastrabbit.com Roast Rabbit Productions], creative writing by Mek <!--- ==Dialogues== * [[/octodon.social/@Megan]] --> 4f585ad8db7fbefaae158f4fd570ab4c8cf18c1b 0 92 316 2022-11-09T02:02:50Z Woozle 1 Created page with "{{fmt/title|the Nix upgrade script issue}} The first step in [https://gitlab.com/tootcat/nixos-config the upgrade] is to start Nix on my desktop -- but I get an error when I d..." wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue}} The first step in [https://gitlab.com/tootcat/nixos-config the upgrade] is to start Nix on my desktop -- but I get an error when I do that: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override My recollection is that I tried the <code>--extra-experimental-features</code> option the last time I ran into this (several months ago), and that led to another dead-end -- but I suppose I could try it again and document that. Yeah, here we go: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features develop warning: unknown experimental feature 'develop' error: no subcommand specified Try 'nix --help' for more information. Am I understanding the error message correctly? Maybe it meant... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied I don't know if that's better or worse. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix/daemon-socket/socket ls: cannot access '/nix/var/nix/daemon-socket/socket': Permission denied woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix/daemon-socket ls: cannot open directory '/nix/var/nix/daemon-socket': Permission denied woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix total 20 drwxr-xr-x 5 root root 4096 Sep 11 15:05 . drwxr-xr-x 3 root root 4096 Sep 11 15:05 .. drwxrwx--- 2 root nix-users 4096 Nov 6 10:45 daemon-socket drwxr-xr-x 3 root root 4096 Sep 11 15:05 gcroots drwxr-xr-x 3 root root 4096 Sep 11 15:05 profiles Anyway, that's where I'm stuck now. b139b6006c9923131ad9fef0fca376443acf9fb7 327 316 2022-11-09T20:44:34Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue}} {{subpage/date}} The first step in [https://gitlab.com/tootcat/nixos-config the upgrade] is to start Nix on my desktop -- but I get an error when I do that: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override My recollection is that I tried the <code>--extra-experimental-features</code> option the last time I ran into this (several months ago), and that led to another dead-end -- but I suppose I could try it again and document that. Yeah, here we go: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features develop warning: unknown experimental feature 'develop' error: no subcommand specified Try 'nix --help' for more information. Am I understanding the error message correctly? Maybe it meant... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied I don't know if that's better or worse. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix/daemon-socket/socket ls: cannot access '/nix/var/nix/daemon-socket/socket': Permission denied woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix/daemon-socket ls: cannot open directory '/nix/var/nix/daemon-socket': Permission denied woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix total 20 drwxr-xr-x 5 root root 4096 Sep 11 15:05 . drwxr-xr-x 3 root root 4096 Sep 11 15:05 .. drwxrwx--- 2 root nix-users 4096 Nov 6 10:45 daemon-socket drwxr-xr-x 3 root root 4096 Sep 11 15:05 gcroots drwxr-xr-x 3 root root 4096 Sep 11 15:05 profiles Anyway, that's where I'm stuck now. 6a173787dc4617eb379f408447442cdf554fb49a 328 327 2022-11-09T20:45:35Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day One}} {{subpage/date}} The first step in [https://gitlab.com/tootcat/nixos-config the upgrade] is to start Nix on my desktop -- but I get an error when I do that: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override My recollection is that I tried the <code>--extra-experimental-features</code> option the last time I ran into this (several months ago), and that led to another dead-end -- but I suppose I could try it again and document that. Yeah, here we go: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features develop warning: unknown experimental feature 'develop' error: no subcommand specified Try 'nix --help' for more information. Am I understanding the error message correctly? Maybe it meant... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied I don't know if that's better or worse. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix/daemon-socket/socket ls: cannot access '/nix/var/nix/daemon-socket/socket': Permission denied woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix/daemon-socket ls: cannot open directory '/nix/var/nix/daemon-socket': Permission denied woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ ls -al /nix/var/nix total 20 drwxr-xr-x 5 root root 4096 Sep 11 15:05 . drwxr-xr-x 3 root root 4096 Sep 11 15:05 .. drwxrwx--- 2 root nix-users 4096 Nov 6 10:45 daemon-socket drwxr-xr-x 3 root root 4096 Sep 11 15:05 gcroots drwxr-xr-x 3 root root 4096 Sep 11 15:05 profiles Anyway, that's where I'm stuck now. b143d97732aa80c9e2d02584fafd98f12b6a7841 10 87 318 306 2022-11-09T13:23:43Z Woozle 1 wikitext text/x-wiki {{c/date|{{PAGENAME}}}} [[category:time]] [[category:date]] {{fmt/title| {{#time: l, F j, Y | {{PAGENAME}}}} {{#time: (#z) | {{PAGENAME}} + 1 day}} }} <table width=100% style="border-bottom: 1px solid green;"><tr><td valign=bottom> <table><tr><td> <table class=wikitable><tr> <td> [[ {{#time: Y/m/d | {{PAGENAME}} - 1 day}} | {{#time: l | {{PAGENAME}} - 1 day}} ]] </td> <td> '''{{#time: l | {{PAGENAME}}}}''' </td> <td> [[ {{#time: Y/m/d | {{PAGENAME}} + 1 day}} | {{#time: l | {{PAGENAME}} + 1 day}} ]] </td> </tr></table> </td><td> {{i/val|status|page=toot.cat}} </td></tr></table> 3398efa17e7a18a8f2a5d98082257012e8b49efd 319 318 2022-11-09T13:24:20Z Woozle 1 wikitext text/x-wiki {{c/date|{{PAGENAME}}}} [[category:time]] [[category:date]] {{fmt/title| {{#time: l, F j, Y | {{PAGENAME}}}} {{#time: (#z) | {{PAGENAME}} + 1 day}} }} <table width=100% style="border-bottom: 1px solid green;"><tr><td valign=bottom> <table width=100%><tr><td valign=top> <table class=wikitable><tr> <td> [[ {{#time: Y/m/d | {{PAGENAME}} - 1 day}} | {{#time: l | {{PAGENAME}} - 1 day}} ]] </td> <td> '''{{#time: l | {{PAGENAME}}}}''' </td> <td> [[ {{#time: Y/m/d | {{PAGENAME}} + 1 day}} | {{#time: l | {{PAGENAME}} + 1 day}} ]] </td> </tr></table> </td><td> {{i/val|status|page=toot.cat}} </td></tr></table> 334b6971c7df2e55e20e45a6a59befa3d365162a 0 93 321 2022-11-09T13:25:25Z Woozle 1 Created page with "{{page/date}} [https://mastodon.radio/@M0YNG/109313981479318698 This post] looks like it has some useful information." wikitext text/x-wiki {{page/date}} [https://mastodon.radio/@M0YNG/109313981479318698 This post] looks like it has some useful information. 9e6fa6a34202e4de32a4d8af2a09d8876a3e27e3 322 321 2022-11-09T13:51:47Z Woozle 1 wikitext text/x-wiki {{page/date}} [https://mastodon.radio/@M0YNG/109313981479318698 This post] looks like it has some useful information. ==Unrelated Discovery== * [https://github.com/vrutkovs/masto-thread-renderer masto-thread-renderer] ([https://social.wildeboer.net/@jwildeboer/109288155629741046 h/t]): takes a Mastodon thread and renders it as Markdown 0295012e48525aec03230404e58b45c769d8e755 335 322 2022-11-09T21:34:22Z Woozle 1 wikitext text/x-wiki {{page/date}} [https://mastodon.radio/@M0YNG/109313981479318698 This post] looks like it has some useful information as far as configuring the queue processes to make better use of CPU resources. Still working on the {{l/sub|Nix issue}}. ==Unrelated Discovery== * [https://github.com/vrutkovs/masto-thread-renderer masto-thread-renderer] ([https://social.wildeboer.net/@jwildeboer/109288155629741046 h/t]): takes a Mastodon thread and renders it as Markdown f467db06aeeee165ef0e04f866e3fc624a3d672f 346 335 2022-11-10T01:47:45Z Woozle 1 wikitext text/x-wiki {{page/date}} [https://mastodon.radio/@M0YNG/109313981479318698 This post] looks like it has some useful information as far as configuring the queue processes to make better use of CPU resources. * Still working on the {{l/sub|Nix issue}} - may be solved, as of end-of-day * [https://toot.cat/@woozle/109316781841682221 Evening status post] ==Unrelated Discovery== * [https://github.com/vrutkovs/masto-thread-renderer masto-thread-renderer] ([https://social.wildeboer.net/@jwildeboer/109288155629741046 h/t]): takes a Mastodon thread and renders it as Markdown 6a8ed9ae462a52faf2c2c8aa5df94c7da54ffd99 10 94 323 2022-11-09T20:38:33Z Woozle 1 Created page with "<table class=wikitable><tr> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} ]] </td> <td> '''{{#time:..." wikitext text/x-wiki <table class=wikitable><tr> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} ]] </td> <td> '''{{#time: l | {{#titleparts:{{PAGENAME}}|3}}}}''' </td> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} + 1 day}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} + 1 day}} ]] </td> 34cb446cbed650bcbd07fe1e19141a674824145c 324 323 2022-11-09T20:39:32Z Woozle 1 wikitext text/x-wiki <table class=wikitable align=right><tr> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} ]] </td> <td> '''{{#time: l | {{#titleparts:{{PAGENAME}}|3}}}}''' </td> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} + 1 day}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} + 1 day}} ]] </td> </table> 95523e9a5546947d2a26040ca75223a014e90427 325 324 2022-11-09T20:41:19Z Woozle 1 wikitext text/x-wiki <table class=wikitable align=right><tr> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} - 1 day}}/{{#titleparts:{{PAGENAME}}|4}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} ]] </td> <td> '''{{#time: l | {{#titleparts:{{PAGENAME}}|3}}}}''' </td> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} + 1 day}}/{{#titleparts:{{PAGENAME}}|4}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} + 1 day}} ]] </td> </table> 3fcfff0038f47c3aa69372ccd184b402823860ba 326 325 2022-11-09T20:43:18Z Woozle 1 wikitext text/x-wiki <table class=wikitable align=right><tr> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} - 1 day}}/{{#titleparts:{{PAGENAME}}||4}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} - 1 day}} ]] </td> <td> '''{{#time: l | {{#titleparts:{{PAGENAME}}|3}}}}''' </td> <td> [[ {{#time: Y/m/d | {{#titleparts:{{PAGENAME}}|3}} + 1 day}}/{{#titleparts:{{PAGENAME}}||4}} | {{#time: l | {{#titleparts:{{PAGENAME}}|3}} + 1 day}} ]] </td> </table> 8f475429cf75019a4d74226bf401a7982a2a94a7 0 95 329 2022-11-09T20:50:29Z Woozle 1 Created page with "{{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user..." wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? bfe7527317a38ce6c415637f8b8a30ce39fbe3b8 332 329 2022-11-09T21:18:41Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. 95c7d53f4c0c7bd9bec7245dcd336ead34456f33 340 332 2022-11-09T21:45:02Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. [SOLVED] 9a3175575de624180b81b775deb48e7d1a6bd58d 341 340 2022-11-09T21:59:42Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied ==Permissions Problem [SOLVED]== Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. [SOLVED] ==Working Here== Take 1: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override Take 2: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop warning: Git tree '/mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' is dirty error: flake 'git+file:///mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' does not provide attribute 'devShells.x86_64-linux.devShell.x86_64-linux', 'packages.x86_64- linux.devShell.x86_64-linux', 'legacyPackages.x86_64-linux.devShell.x86_64-linux', 'devShell.x86_64-linux' or 'defaultPackage.x86_64-linux' Hmm... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git pull origin Already up to date. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status "git-crypt" clean: 1: git-crypt: not found error: external filter '"git-crypt" clean' failed 127 error: external filter '"git-crypt" clean' failed fatal: secrets/mastodon/aws-secret-access-key: clean filter 'git-crypt' failed Well, that obviously means something. 0a23a2211f195ac589a7e9dd586a16de3ad7dff4 342 341 2022-11-09T22:39:55Z Woozle 1 /* Working Here */ wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied ==Permissions Problem [SOLVED]== Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. [SOLVED] ==Working Here== Take 1: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override Take 2: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop warning: Git tree '/mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' is dirty error: flake 'git+file:///mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' does not provide attribute 'devShells.x86_64-linux.devShell.x86_64-linux', 'packages.x86_64- linux.devShell.x86_64-linux', 'legacyPackages.x86_64-linux.devShell.x86_64-linux', 'devShell.x86_64-linux' or 'defaultPackage.x86_64-linux' Hmm... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git pull origin Already up to date. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status "git-crypt" clean: 1: git-crypt: not found error: external filter '"git-crypt" clean' failed 127 error: external filter '"git-crypt" clean' failed fatal: secrets/mastodon/aws-secret-access-key: clean filter 'git-crypt' failed Well, that obviously means something. After installing <code>git-crypt</code> on the local system (which feels a bit like whacking the side of the TV, as opposed to knowing what I'm doing), it's now this: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: update.sh no changes added to commit (use "git add" and/or "git commit -a") 66f954c4ef041e7bedcb2234e027cde3194e3bf6 343 342 2022-11-09T22:41:08Z Woozle 1 /* Working Here */ wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied ==Permissions Problem [SOLVED]== Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. [SOLVED] ==Working Here== Take 1: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override Take 2: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop warning: Git tree '/mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' is dirty error: flake 'git+file:///mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' does not provide attribute 'devShells.x86_64-linux.devShell.x86_64-linux', 'packages.x86_64- linux.devShell.x86_64-linux', 'legacyPackages.x86_64-linux.devShell.x86_64-linux', 'devShell.x86_64-linux' or 'defaultPackage.x86_64-linux' Hmm... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git pull origin Already up to date. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status "git-crypt" clean: 1: git-crypt: not found error: external filter '"git-crypt" clean' failed 127 error: external filter '"git-crypt" clean' failed fatal: secrets/mastodon/aws-secret-access-key: clean filter 'git-crypt' failed Well, that obviously means something. After installing <code>git-crypt</code> on the local system (which feels a bit like whacking the side of the TV, as opposed to knowing what I'm doing), it's now this: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: update.sh no changes added to commit (use "git add" and/or "git commit -a") ...but the nix command still gives the same error. cdd18fb6f1d36f29367018c9d65acd806d43c901 344 343 2022-11-10T00:50:32Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied ==Permissions Problem [SOLVED]== Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. [SOLVED] ==Where I Was== Take 1: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override Take 2: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop warning: Git tree '/mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' is dirty error: flake 'git+file:///mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' does not provide attribute 'devShells.x86_64-linux.devShell.x86_64-linux', 'packages.x86_64- linux.devShell.x86_64-linux', 'legacyPackages.x86_64-linux.devShell.x86_64-linux', 'devShell.x86_64-linux' or 'defaultPackage.x86_64-linux' Hmm... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git pull origin Already up to date. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status "git-crypt" clean: 1: git-crypt: not found error: external filter '"git-crypt" clean' failed 127 error: external filter '"git-crypt" clean' failed fatal: secrets/mastodon/aws-secret-access-key: clean filter 'git-crypt' failed Well, that obviously means something. After installing <code>git-crypt</code> on the local system (which feels a bit like whacking the side of the TV, as opposed to knowing what I'm doing), it's now this: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: update.sh no changes added to commit (use "git add" and/or "git commit -a") ...but the nix command still gives the same error. ==Where We Are== ...and then Nixpert seriously dived in and first helped me figure out a bunch of stuff, and then tidied up the repo and ran a merge of the latest GlitchSoc repo, and now we're doing a backup before finally running the update. The backup may take too long to finish today, but it looks like the upgrade should happen in the next 24 hours. 5aa9d0995641e6f0d9b11af842c2fa03c13278a2 345 344 2022-11-10T00:51:25Z Woozle 1 /* Where We Are */ wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Two}} {{subpage/date}} [https://toot.cat/@jhelwig/109314571331799093 Jacob Helwig suggested] that I look at user groups. My user (<code>woozle</code>, i.e. my usual login on this machine) is indeed ''not'' in the <code>nix-users</code> group -- but adding myself to the <code>nix-users</code> group doesn't seem to help: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied ==Permissions Problem [SOLVED]== Invoking sudo does at least produce a different result: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override I don't recall needing to jump through these hoops when I first ran this script, successfully, some months ago... but maybe it makes a difference that I'm now using a distro (Linux Mint 21) that is a little bit behind the distro I was using then (Ubuntu-MATE 22.04). Maybe Nix can be used to update itself to the most recent version? A Nixpert (I don't know if she wants credit/identification) in the TootCat Discord is providing me with some more information, as is shadow!admin. The following command should override the error messages: nix --extra-experimental-features 'nix-command flakes' develop Explanation for why "develop" is outside the single-quotes: "develop is a subcommand. this is just nix develop but with some features enabled." I don't entirely understand that, but maybe it will make sense later, and it gives me a bit more context. error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied [[/sidetrack]]: why won't {{l/htyp|usermod}} work. [SOLVED] ==Where I Was== Take 1: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix develop --extra-experimental-features nix-command error: experimental Nix feature 'flakes' is disabled; use '--extra-experimental-features flakes' to override Take 2: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ nix --extra-experimental-features 'nix-command flakes' develop warning: Git tree '/mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' is dirty error: flake 'git+file:///mnt/teralap/home/woozle/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config' does not provide attribute 'devShells.x86_64-linux.devShell.x86_64-linux', 'packages.x86_64- linux.devShell.x86_64-linux', 'legacyPackages.x86_64-linux.devShell.x86_64-linux', 'devShell.x86_64-linux' or 'defaultPackage.x86_64-linux' Hmm... woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git pull origin Already up to date. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status "git-crypt" clean: 1: git-crypt: not found error: external filter '"git-crypt" clean' failed 127 error: external filter '"git-crypt" clean' failed fatal: secrets/mastodon/aws-secret-access-key: clean filter 'git-crypt' failed Well, that obviously means something. After installing <code>git-crypt</code> on the local system (which feels a bit like whacking the side of the TV, as opposed to knowing what I'm doing), it's now this: woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: update.sh no changes added to commit (use "git add" and/or "git commit -a") ...but the nix command still gives the same error. ==Where We Are== ...and then Nixpert seriously dived in and first helped me figure out a bunch of stuff, and then tidied up the repo and ran a merge of the latest GlitchSoc repo, and now we're doing a backup before finally running the update. The backup may take too long to finish today, but it looks like the upgrade should happen in the next 24 hours. Once that's done, there's some documentation to be updated and also the backup routines need to be fixed. 3150aa0df588185774a8fd988ae44d567f8ae890 0 96 330 2022-11-09T21:17:39Z Woozle 1 Created page with "'''Figured out a thing''': When I added myself to <code>nix-users</code> earlier, it didn't actually work. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/To..." wikitext text/x-wiki '''Figured out a thing''': When I added myself to <code>nix-users</code> earlier, it didn't actually work. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo usermod -a -G nix-users woozle woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare 75686576d8148ceab9830c2a64bcad09a786c79d 334 330 2022-11-09T21:26:52Z Woozle 1 wikitext text/x-wiki '''Figured out a thing''': When I added myself to <code>nix-users</code> earlier, it didn't actually work. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo usermod -a -G nix-users woozle woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare For extra bafflement, the Control Panel user-management applet clearly shows that yes, I am in fact a member in good standing of the illustrious <code>nix-users-</code> group: [[File:2022-11-09 16-22-40.screen.nix-users group.png]] Even if I start a new <code>bash</code> session, however, "groups" still doesn't list it. I'd suspect that it's hidden somehow, if it weren't for the fact that <code>ls</code> is acting like my membership is invalid. I'm beginning to suspect some kind of Good Old <s>Boy</s> Code Network in operation here... 96cb25d75a7752e74c3be6dac4be401ec787ef30 338 334 2022-11-09T21:36:47Z Woozle 1 wikitext text/x-wiki '''Figured out a thing''': When I added myself to <code>nix-users</code> earlier, it didn't actually work. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo usermod -a -G nix-users woozle woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare For extra bafflement, the Control Panel user-management applet clearly shows that yes, I am in fact a member in good standing of the illustrious <code>nix-users</code> group: [[File:2022-11-09 16-22-40.screen.nix-users group.png]] Even if I start a new <code>bash</code> session, however, "groups" still doesn't list it. I'd suspect that it's hidden somehow, if it weren't for the fact that <code>ls</code> is acting like my membership is invalid. I'm beginning to suspect some kind of Good Old <s>Boy</s> Code Network in operation here... 229b0b0cdf7dce286c6a22fbd4483379bca538eb 339 338 2022-11-09T21:44:44Z Woozle 1 wikitext text/x-wiki '''Figured out a thing''': When I added myself to <code>nix-users</code> earlier, it didn't actually work. woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ sudo usermod -a -G nix-users woozle woozle@SamEagle:~/nextcloud/statler/woozle/projects/web/Mastodon/TootCat/nixos-config$ groups woozle adm cdrom sudo dip plugdev lpadmin sambashare For extra bafflement, the Control Panel user-management applet clearly shows that yes, I am in fact a member in good standing of the illustrious <code>nix-users</code> group: [[File:2022-11-09 16-22-40.screen.nix-users group.png]] Even if I start a new <code>bash</code> session, however, "groups" still doesn't list it. I'd suspect that it's hidden somehow, if it weren't for the fact that <code>ls</code> is acting like my membership is invalid. I'm beginning to suspect some kind of Good Old <s>Boy</s> Code Network in operation here... ==Solution== ghost!admin pointed out that opening a new terminal session does ''not'' log in again, and the new group membership won't take effect until the next login. This command does: sudo login woozle d7a4df357dc6b61ffebc427e028fc8dd44e6e0ab 10 97 331 2022-11-09T21:18:26Z Woozle 1 Created page with "[[htyp:{{{1}}}|{{{2|{{{1}}}}}}]]" wikitext text/x-wiki [[htyp:{{{1}}}|{{{2|{{{1}}}}}}]] 7b78dda3190a9bb0a35db6cc4f3786f3dfb8c350 6 98 333 2022-11-09T21:24:01Z Woozle 1 [[catgegory:screenshot]] {{c/date|2022-11-09}} * '''what''': screenshot showing that "woozle" is in fact a member of the "nix-users" group wikitext text/x-wiki == Summary == [[catgegory:screenshot]] {{c/date|2022-11-09}} * '''what''': screenshot showing that "woozle" is in fact a member of the "nix-users" group 70732d1cb0a991dae4a5718595c462576043d8d6 336 333 2022-11-09T21:35:09Z Woozle 1 wikitext text/x-wiki == Summary == [[category:screenshot]] {{c/date|2022-11-09}} * '''what''': screenshot showing that "woozle" is in fact a member of the "nix-users" group 78423204caeb783e9286e2cedd268154dbbbe865 14 99 337 2022-11-09T21:35:57Z Woozle 1 Created page with "any upload that is (or is mainly) a screenshot" wikitext text/x-wiki any upload that is (or is mainly) a screenshot e7a561d64f9f309517a45a0726953bda4f76134b 0 100 347 2022-11-10T14:27:58Z Woozle 1 Created page with "{{page/date}} * Update attempt failed, for ''new'' reasons. Looks like a configuration problem. I am seeking assistance, which probably isn't awake yet. * I am ''so'' snagging..." wikitext text/x-wiki {{page/date}} * Update attempt failed, for ''new'' reasons. Looks like a configuration problem. I am seeking assistance, which probably isn't awake yet. * I am ''so'' snagging [https://toot.cat/@ionizedgirl/109319902515900718 this] for an eventual t-shirt or something. 9ce5a8f06537e256e730c1a8e9db9e3b9e0d28fd 350 347 2022-11-10T16:59:40Z Woozle 1 wikitext text/x-wiki {{page/date}} * Update attempt failed, for [[/Nix issue|''new'' reasons]]. Looks like a configuration problem. I am seeking assistance, which probably isn't awake yet. * I am ''so'' snagging [https://toot.cat/@ionizedgirl/109319902515900718 this] for an eventual t-shirt or something. 6d690dc7c8dda6a4b490cf37d09007ecae52e925 6 101 348 2022-11-10T16:54:53Z Woozle 1 [[category:screenshot]] [[category:CLI]] * '''what''': screenshot of <code>colmena apply</code> not working wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:CLI]] * '''what''': screenshot of <code>colmena apply</code> not working 16f4b4245b3d7db7dfe54d1ced7b7487e4464580 0 102 349 2022-11-10T16:58:57Z Woozle 1 Created page with "{{fmt/title|the Nix upgrade script issue: Day Three}} {{subpage/date}} We actually made a lot of progress last night, thanks to Nixpert and ghost!admin. Working: * nix devel..." wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Three}} {{subpage/date}} We actually made a lot of progress last night, thanks to Nixpert and ghost!admin. Working: * nix develop * update.sh [[File:2022-11-10.screen.colmena apply error.png|thumb|left|colmena does not apply]]Starts, but fails: * colmena apply I'm now trying to figure out where this thing might be defined -- or is supposed to be defined, but isn't -- that is resulting in the "Error: hash mismatch, expected undefined, got 5f1715e506e71860b4b07c50060ea6462217611e" message. Running <code>nix log /nix/store/k0q66yrcfzsq3llgr13m928xqiqkgcm8-offline.drv</code>, as it suggests, just gives me a ">" prompt (and would presumably show those last 10 lines again, plus whatever came before -- but everything was working until the last 5 lines, so I don't know what I might get from that... unless it names the file it's looking at which has the missing definition...?). 36e9115487a41b3c2292f165c75abb1c5081ff33 352 349 2022-11-11T20:15:09Z Woozle 1 wikitext text/x-wiki {{fmt/title|the Nix upgrade script issue: Day Three}} {{subpage/date}} We actually made a lot of progress last night, thanks to Nixpert and ghost!admin. Working: * nix develop * update.sh [[File:2022-11-10.screen.colmena apply error.png|thumb|left|colmena does not apply]]Starts, but fails: * colmena apply I'm now trying to figure out where this thing might be defined -- or is supposed to be defined, but isn't -- that is resulting in the "Error: hash mismatch, expected undefined, got 5f1715e506e71860b4b07c50060ea6462217611e" message. Running <code>nix log /nix/store/k0q66yrcfzsq3llgr13m928xqiqkgcm8-offline.drv</code>, as it suggests, just gives me a ">" prompt (and would presumably show those last 10 lines again, plus whatever came before -- but everything was working until the last 5 lines, so I don't know what I might get from that... unless it names the file it's looking at which has the missing definition...?). '''Post-hoc update''': We did finally get it working. Now we just need to tweak some things... 7e4714f910a7980151decdea4b733a4d3baee042 0 89 351 308 2022-11-10T17:02:01Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-10 12:00 EST''' toot.cat is still a bit slow and cranky.|Uploads seem to work (reluctantly) in the morning, and everything gets gradually worse as the day progresses.}} 6279a93028fbf536141accbbfe2d6e8341a2d623 354 351 2022-11-11T20:23:34Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-11 15:23 EST''' toot.cat is still a bit slow and cranky.|Uploads seem to be working well, however.}} 347f0293527e47b92d6bc00a2918a97c556d9755 0 103 353 2022-11-11T20:18:30Z Woozle 1 Created page with "{{page/date}} * '''14:53 EST''' [https://toot.cat/@woozle/109326921792556208 post about Masto favicons and documentation]" wikitext text/x-wiki {{page/date}} * '''14:53 EST''' [https://toot.cat/@woozle/109326921792556208 post about Masto favicons and documentation] 82b47b61c4edfb3d846f07cbf82f45fec7f0b8c9 355 353 2022-11-11T20:51:24Z Woozle 1 wikitext text/x-wiki {{page/date}} * '''14:53 EST''' [https://toot.cat/@woozle/109326921792556208 post about Masto favicons and documentation] ...and I'm still not at all sure {where in the Nix config} the load-optimizations settings are, but I need to mostly break from working on this for a day or so. A thing for me to look at later: [https://github.com/vivlim/nixpkgs/blob/tootcat/nixos/modules/services/web-apps/mastodon.nix mastodon.nix] is where the stuff defined in configuration.nix gets built into the actual Mastodon config (presumably including the various standard Masto config files), according to Nixpert. 333c70d8469a5488a5d7014cf1f26ce602b486be 0 42 356 220 2022-11-12T14:54:23Z Woozle 1 Woozle moved page [[Pub/.cat]] to [[.cat]]: all space is now public; no need for "pub" in title wikitext text/x-wiki The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about {{l/pub|Catalonia}} as it comes our way. * We are interested in making space for content related to Catalonia and/or {{l/pub|Catalan}}. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|blob.cat}}: a [[Pleroma]] instance * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Mastodon user Sam Toland [https://social.coop/@samtoland/100152739177441119 notes] that the .cat admins used to be much stricter, but have now loosened enforcement a bit. 66246914f7a2b7e645933b44ed8df1fa478a5285 358 356 2022-11-12T14:55:40Z Woozle 1 wikitext text/x-wiki The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about [[Catalonia]] as it comes our way. * We are interested in making space for content related to Catalonia and/or [[Catalan]]. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|blob.cat}}: a [[Pleroma]] instance * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Mastodon user Sam Toland [https://social.coop/@samtoland/100152739177441119 notes] that the .cat admins used to be much stricter, but have now loosened enforcement a bit. e678fcbe3981cf19344a426b94f6dd97a7268bc3 0 67 359 242 2022-11-12T14:56:02Z Woozle 1 Woozle moved page [[Pub/2020-03-31]] to [[2020-03-31]]: eliminating "pub" wikitext text/x-wiki * '''19:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''19:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''20:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. * '''20:35''' Snapshot done; resizing. "Resizing can take up to 1 minute per GB of data used by your Droplet." We've got a mostly-full 80 GB drive to resize with, so about an hour. * '''21:02''' [https://toot.cat/@woozle/103920629656934017 Back online!] 838715e897e4f98567b7f2eb3f514e33717afac4 361 359 2022-11-12T14:56:25Z Woozle 1 wikitext text/x-wiki {{page/date}} * '''19:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''19:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''20:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. * '''20:35''' Snapshot done; resizing. "Resizing can take up to 1 minute per GB of data used by your Droplet." We've got a mostly-full 80 GB drive to resize with, so about an hour. * '''21:02''' [https://toot.cat/@woozle/103920629656934017 Back online!] 4cd5ca49451cf2fddce75c75dcb366cde9c4f59e 0 56 362 194 2022-11-12T14:56:58Z Woozle 1 Woozle moved page [[Pub/Catalan]] to [[Catalan]]: eliminating "pub" wikitext text/x-wiki some cover songs possibly in Catalan (hey, it's all I've been able to find so far!): * [https://www.youtube.com/watch?v=Bw6Q9GiVaYw Mr Tambourine Man - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=t17tD0ByhR4 500 Millas - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=GFav2hjkLjE 12. Arriba la nit - Txarango] * [https://www.youtube.com/watch?v=e2pEx7PAb30 Txarango - Agafant l'horitzó (ft. G. Humet, Aspencat, C. Freixas, Les Kol·lontai i Ascensa Furore)] ==Reference== * [[wikipedia:Catalan language|Wikipedia]] 5457bbb7f2c9bc6d84197341d30f08e4b20b7377 0 106 363 2022-11-12T14:56:58Z Woozle 1 Woozle moved page [[Pub/Catalan]] to [[Catalan]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Catalan]] 200ab3c8d2ffadc4ce0c1d81ed2e57e26bddc87e 0 29 364 104 2022-11-12T14:57:19Z Woozle 1 Woozle moved page [[Pub/Catalonia]] to [[Catalonia]]: eliminating "pub" wikitext text/x-wiki ==Links== ===Events=== * '''2018-06-13''' [https://www.cooperativestreball.coop/esdeveniments/2018/06/05/benvingudes-noves-cooperatives Benvingudes noves cooperatives] (auto-translated) "A session for the recently federated cooperatives to approach the Federation of Cooperatives of Work of Catalonia and know in detail who we are, what we do and how we organize." ===Video=== * [https://exode.me/videos/watch/a4d6ebb3-8f61-48c7-88fd-3246de039725 History of Catalonia] a5dee6ca65d4fa3bd4c9bb4dd94d8aa626362a58 0 107 365 2022-11-12T14:57:19Z Woozle 1 Woozle moved page [[Pub/Catalonia]] to [[Catalonia]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Catalonia]] 8cf534f0d0ba135abe2bd41d1d01f8a039ceb572 0 47 366 221 2022-11-12T14:57:39Z Woozle 1 Woozle moved page [[Pub/ForkTogether]] to [[ForkTogether]]: eliminating "pub" wikitext text/x-wiki Everything that was here has been moved to [https://wiki.florencesoc.org the Florence wiki]. 521b38f459ae6e1e371f142efba5e39c46441784 368 366 2022-11-12T14:58:54Z Woozle 1 wikitext text/x-wiki Everything that was here has been moved to <s>[https://wiki.florencesoc.org the Florence wiki]</s> (no longer online; if I was hosting that, then I probably have a backup of the data. [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:58, 12 November 2022 (UTC)). 1e6b4919861218c9156a4ed1a5223f6e2230f8c1 369 368 2022-11-12T14:59:14Z Woozle 1 wikitext text/x-wiki [[category:defunct]] Everything that was here has been moved to <s>[https://wiki.florencesoc.org the Florence wiki]</s> (no longer online; if I was hosting that, then I probably have a backup of the data. [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:58, 12 November 2022 (UTC)). b08ddba764a38d3bfdb6d850ae77d2a9da8e93c6 0 108 367 2022-11-12T14:57:39Z Woozle 1 Woozle moved page [[Pub/ForkTogether]] to [[ForkTogether]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[ForkTogether]] 4b2dc77c298d1ab6180691684d537865f95834d2 0 64 370 216 2022-11-12T14:59:35Z Woozle 1 Woozle moved page [[Pub/Gab]] to [[Gab]]: eliminating "pub" wikitext text/x-wiki '''Gab''' is a build of Mastodon. It appears to have a reputation as being popular with {{l/ip|frozen fruit}} advocates. ==Links== * [https://fediverse.network/mastodon?build=gab instances using Gab] 323fcc642132b077cf1f194a6c07e54afd8377f5 372 370 2022-11-12T15:00:52Z Woozle 1 wikitext text/x-wiki [[category:fork]] '''Gab''' is a build of Mastodon. It appears to have a reputation as being popular with {{l/ip|frozen fruit}} advocates. ==Links== * [https://fediverse.network/mastodon?build=gab instances using Gab] ef65b5b7d28098b72774d45967da9cb075110b39 0 109 371 2022-11-12T14:59:35Z Woozle 1 Woozle moved page [[Pub/Gab]] to [[Gab]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Gab]] cd50bfc8c7cb9f5984ba6cbee533990caee2c032 0 40 373 120 2022-11-12T15:01:23Z Woozle 1 Woozle moved page [[Pub/Mastodon]] to [[Mastodon]]: eliminating "pub" wikitext text/x-wiki ==Problematicity== ===Arbitrary Decisions=== * '''2018-06-28''' [https://is.a.qute.dog/@KS/703046 Sorting by "most recent activity" immediately shows you that he mass closed every open issue that @hoodie made.] ===Trending Tags=== * '''2018.06.04''' [https://social.coop/@kittybecca/100145873112206294 yesterday apparently the hashtag DropTheT trended on twitter...]: one reason why trending tags is a problematic feature * '''2018.06.03''' ** [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. ** [https://elekk.xyz/@maloki/100141486585398752 What is ForkOff/Together?] * '''2018.06.01-03''' [https://github.com/tootsuite/mastodon/issues/7702 GitHub issue #7702: Admin Option to Disable Trending Feature] ** '''2018.06.03''' [https://mastodon.social/@Gargron/100140965702165118 I've locked the discussion so nobody can comment on it anymore but...] 3199181fb2ef121ca77fc6a9fccd42aff6e775ac 375 373 2022-11-12T15:02:28Z Woozle 1 wikitext text/x-wiki [[category:software]] ==Problematicity== ===Arbitrary Decisions=== * '''2018-06-28''' [https://is.a.qute.dog/@KS/703046 Sorting by "most recent activity" immediately shows you that he mass closed every open issue that @hoodie made.] ===Trending Tags=== * '''2018.06.04''' [https://social.coop/@kittybecca/100145873112206294 yesterday apparently the hashtag DropTheT trended on twitter...]: one reason why trending tags is a problematic feature * '''2018.06.03''' ** [https://dev.glitch.social/@cassolotl/100140423395298541 Cas makes some points] before retreating to the safety of Twitter. ** [https://elekk.xyz/@maloki/100141486585398752 What is ForkOff/Together?] * '''2018.06.01-03''' [https://github.com/tootsuite/mastodon/issues/7702 GitHub issue #7702: Admin Option to Disable Trending Feature] ** '''2018.06.03''' [https://mastodon.social/@Gargron/100140965702165118 I've locked the discussion so nobody can comment on it anymore but...] 835a568def10c7b41c8ed636cc79cd3d7e867e65 0 110 374 2022-11-12T15:01:23Z Woozle 1 Woozle moved page [[Pub/Mastodon]] to [[Mastodon]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Mastodon]] 64fbc0d04571dfcfcd7aef6d6e915e1bda6a05bc 0 38 376 119 2022-11-12T15:03:44Z Woozle 1 wikitext text/x-wiki The '''Mastoverse''' is the [[Mastodon]]-compatible {{l/htyp|fediverse}}, i.e. all the federated Mastodon instances as well as instances of other software that federates with Mastodon (including GNUSocial and Pleroma). ==Pages== * {{lc|instances}}: list of instances we have pages about 9a980d08dbd73ec65d2c94f1d712cc7831c4cc5a 377 376 2022-11-12T15:03:59Z Woozle 1 Woozle moved page [[Pub/Mastoverse]] to [[Mastoverse]]: eliminating "pub" wikitext text/x-wiki The '''Mastoverse''' is the [[Mastodon]]-compatible {{l/htyp|fediverse}}, i.e. all the federated Mastodon instances as well as instances of other software that federates with Mastodon (including GNUSocial and Pleroma). ==Pages== * {{lc|instances}}: list of instances we have pages about 9a980d08dbd73ec65d2c94f1d712cc7831c4cc5a 0 111 378 2022-11-12T15:03:59Z Woozle 1 Woozle moved page [[Pub/Mastoverse]] to [[Mastoverse]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Mastoverse]] b6e97fd5431f807211610d4b8473187d092db2d9 0 34 379 80 2022-11-12T15:04:54Z Woozle 1 Woozle moved page [[Pub/TootCave]] to [[TootCave]]: eliminating "pub" wikitext text/x-wiki ='''The TootCave'''= ''aka [https://toot.cat/web/accounts/1132 @Harena]'s basement'' This is where {{lpub/user|woozle}} retreats to brood over the state of humanity and also to fix server stuff and sometimes code. [[File:IMG 20180520 140507818.jpg|thumb|left|500px|The wall bears strange inscriptions from another epoch.<br>Also, old trampoline parts.]] [[File:IMG 20180520 140536048.jpg|thumb|right|500px|The tools of world domination]] [[File:IMG 20180520 140549054.jpg|thumb|left|800px|The Seat of Power -- from which Woozle hears all, sees all, knows all]] 9e61b675fbf9578dbcdcc58f7d059b2fb7fb86fb 398 379 2022-11-12T15:32:32Z Woozle 1 wikitext text/x-wiki ='''The TootCave'''= ''aka [https://toot.cat/web/accounts/1132 @Harena]'s basement'' This is was, at one time, where {{lpub/user|woozle}} would retreat to brood over the state of humanity and also to fix server stuff and sometimes code. (Woozle was at the time using a Moto G4 with a scratchy camera lens; we apologize for the glare.) We should probably designate the office at Hypertwin Manor (and its {{l/htw|Couch of Awesome}}) as the new TootCave. [[File:IMG 20180520 140507818.jpg|thumb|left|500px|The wall bears strange inscriptions from another epoch.<br>Also, old trampoline parts.]] [[File:IMG 20180520 140536048.jpg|thumb|right|500px|The tools of world domination]] [[File:IMG 20180520 140549054.jpg|thumb|left|800px|The Seat of Power -- from which Woozle hears all, sees all, knows all]] 22bb21b345943de47b24f91739ae4a367bde7ad3 399 398 2022-11-12T15:33:13Z Woozle 1 wikitext text/x-wiki {{fmt/title|The TootCave|aka [https://toot.cat/web/accounts/1132 @Harena]'s basement}} This is was, at one time, where {{lpub/user|woozle}} would retreat to brood over the state of humanity and also to fix server stuff and sometimes code. (Woozle was at the time using a Moto G4 with a scratchy camera lens; we apologize for the glare.) We should probably designate the office at Hypertwin Manor (and its {{l/htw|Couch of Awesome}}) as the new TootCave. [[File:IMG 20180520 140507818.jpg|thumb|left|500px|The wall bears strange inscriptions from another epoch.<br>Also, old trampoline parts.]] [[File:IMG 20180520 140536048.jpg|thumb|right|500px|The tools of world domination]] [[File:IMG 20180520 140549054.jpg|thumb|left|800px|The Seat of Power -- from which Woozle hears all, sees all, knows all]] f4ff8ae385058140fa86a7525176567ab53dce5b 0 112 380 2022-11-12T15:04:54Z Woozle 1 Woozle moved page [[Pub/TootCave]] to [[TootCave]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[TootCave]] 0e649fcb1fe3d17da22cf4a7474c68c3d97fbf22 10 113 381 2022-11-12T15:08:47Z Woozle 1 Created page with "[[htwiki:{{{1}}}|{{{2|{{{1}}}}}}]]" wikitext text/x-wiki [[htwiki:{{{1}}}|{{{2|{{{1}}}}}}]] 3923cf7056893c56f3e17f38802aa5cece9f5d45 0 52 382 180 2022-11-12T15:12:25Z Woozle 1 wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since [[toot.cat]] is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@eddy Eddy] (a smol orange tabby girl cat) * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@Lady Lady] (a bicolor medium-length street cat with feline herpes) * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@meowra meowra] (Onyx and Rudy) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ===cat people=== * [https://toot.cat/@KittyMinT mint] "im mint and im like cats." * [https://toot.cat/@oscelot Oscelot] -- [https://toot.cat/@oscelot/100585328496929184 claims] not to be cat-related, but profile also says "cat". We are confused. ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" 0b8b3add1cd8f4a330c3167ddba642c6289fffb6 383 382 2022-11-12T15:12:45Z Woozle 1 Woozle moved page [[Pub/cat]] to [[Cat]]: eliminating "pub" wikitext text/x-wiki [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since [[toot.cat]] is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@eddy Eddy] (a smol orange tabby girl cat) * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@Lady Lady] (a bicolor medium-length street cat with feline herpes) * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@meowra meowra] (Onyx and Rudy) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ===cat people=== * [https://toot.cat/@KittyMinT mint] "im mint and im like cats." * [https://toot.cat/@oscelot Oscelot] -- [https://toot.cat/@oscelot/100585328496929184 claims] not to be cat-related, but profile also says "cat". We are confused. ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" 0b8b3add1cd8f4a330c3167ddba642c6289fffb6 0 114 384 2022-11-12T15:12:45Z Woozle 1 Woozle moved page [[Pub/cat]] to [[Cat]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Cat]] 1efccf44bebc3832919bec322adfdb911cdc76c4 0 60 385 202 2022-11-12T15:13:13Z Woozle 1 Woozle moved page [[Pub/daffodil-11.org]] to [[Daffodil-11.org]]: eliminating "pub" wikitext text/x-wiki [[category:instances]] A strange instance with no descriptor; trying to figure out what they're up to. * [https://daffodil-11.org/@pleasetouch_me @pleasetouch_me] followed me on Hubzilla. Kind of creepy name. * [https://daffodil-11.org/@moanlisa @moanlisa] - followbot? user report: "Every account on this instance is mass-following people." * [https://daffodil-11.org/@gunner @gunner] - followbot? ebbc477d6a6c6149f65af7f7554a58d345199a49 387 385 2022-11-12T15:14:36Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:defunct]] Formerly a strange instance with no descriptor. As of 2022-11-12, they do not seem to be hosting a social media site (or at least not one that's publicly accessible). * [https://daffodil-11.org/@pleasetouch_me @pleasetouch_me] followed me on Hubzilla. Kind of creepy name. * [https://daffodil-11.org/@moanlisa @moanlisa] - followbot? user report: "Every account on this instance is mass-following people." * [https://daffodil-11.org/@gunner @gunner] - followbot? 538ed99cdf1e88ce6781754f122df38c8584f6ad 0 115 386 2022-11-12T15:13:13Z Woozle 1 Woozle moved page [[Pub/daffodil-11.org]] to [[Daffodil-11.org]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Daffodil-11.org]] eb8b23a0976c1eacd108246a624f04f9144ac2c6 0 16 388 205 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle]] to [[Woozle]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. Also, have some photos of The {{l/pub|TootCave}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} * {{ld/blog|2018-04-07|sketching a code}} ==Pages== * {{l/sub|GlitchSoc}}: feature requests * {{l/sub|malusers}} 035507fda19b47662f66b5f3bbdfe4ebab41b307 0 116 389 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle]] to [[Woozle]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki #REDIRECT [[Woozle]] ac677a6740802f59df1ff1333c7223253bac2b8f 0 22 390 46 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/2018/04/05/justice in the fediverse]] to [[Woozle/2018/04/05/justice in the fediverse]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki {{box/principles| : I strive to evaluate first in terms of potential harm. : I strive not to decide until I have all the facts. }} I'm working towards a redesigned process of justice. What I've come up with isn't as radically revisioned as what I'd like to do in the long run, but I don't have the tools for that yet. Traditional justice systems are usually based on hierarchies &ndash; something that has harmed many of us and which I believe most of us want to move away from. Justice should empower us all equally. Ideally, a system of justice would rely more on rallying our common sense of empathy<ref name=sydney /> to create the authority necessary to exercise power against malicious acts. To do that, we need tools that let us nurture and empower empathy, and disempower selfishness. We're not there yet. What we do have now is: * a fediverse, with a very simple and fairly short hierarchy: instance admins on the upper layer and regular users on the lower, with relatively minor and variable differences in power on each level, and * this wiki, in which I hope we can build a copyable navigation aid for uncertain waters &ndash; a reference index, a catalog of findable landmarks. It has fallen naturally to the instance admins to administer justice &ndash; and yet we barely have the seeds of a set of best practices. We've done well crafting our Codes of Conduct to define the responsibilities of our users &ndash; but recent events have shown that we need Codes of Justice, to define (and limit) the responsibilities of our admins. Power must be accountable, and must be earned through its use in the service of the disempowered<ref name=banazi /> or else it is illegitimate. A Code of Justice needs to be able to answer certain questions: * As a user, how can I seek redress for harm done to me? * As an admin &mdash; ** under what circumstances am I enabled to act? ** under what circumstances do I have some moral obligation to act? ** what are the limits of the actions I may take? There are many different reasonable answers to these questions; I'm going to try to set out some for me to follow as admin of toot.cat. ==Footnotes== <references> <ref name=sydney>Apparently I now have a Sydney head-squirrel because I'm hearing strenuous objections to the idea that we could ever rely on any such thing, especially not now, and she's really quite skeptical that such a thing really exists in the first place, so the idea of depending on it for our safety is really kind of hecking scary. I'm... not ignoring her, but deferring that discussion for a later time; my statement was speculative and I agree we're not ready to go there yet.</ref> <ref name=banazi>This is essentially why we penalize instances that enable right-wing propaganda: they are failing in their service to the disempowered. They fail to protect the weak from the strength of induced collective hostility.</ref> </references> 11ccbe1756e47d9e535bd3675d618d74636006d3 0 117 391 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/2018/04/05/justice in the fediverse]] to [[Woozle/2018/04/05/justice in the fediverse]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki #REDIRECT [[Woozle/2018/04/05/justice in the fediverse]] 2e51555fb58ec6c692f9452cc33174ec083ed7a7 0 24 392 48 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/2018/04/07/sketching a code]] to [[Woozle/2018/04/07/sketching a code]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki {{box/principles| : Words have consequences. : All accusations should be taken seriously. : No accusation should be accepted as truth unless the evidence supports it. : Both accusers and accused may need some protection. : A lie often contains just enough truth to make it plausible. }} ==Public Intervention Process<ref name=pip />== Other instances may adopt this, modify it, or ignore it completely; I'm content to let the marketplace of kindness<ref name=note1 /> decide whether such a thing is necessary or not, and to let the process of considered discussion refine it as needed &ndash; but tentatively, here's the way I think it should work for toot.cat. '''If you have a grievance against another user'''<ref name=note2 /> and would like me (as sysop of this instance) to do something about it: # "@" me (@woozle@toot.cat) with a public<ref name=public /> toot stating the nature of the problem and that you are requesting an Intervention. #* The primary types of problem I expect to be addressing are: (a) someone has abused you, or (b) someone has falsely accused you of abuse &ndash; but others may emerge. # This means I have your permission to investigate the situation and publicly post my findings on Mew (this wiki). #* I will probably need to ask a lot of nosy questions, both to you and the other parties involved. Let me know if you anticipate any problems with this. #* These discussions should take place on Mastodon<ref name=mastodm /> so as to be part of the public record, though I can make exceptions if there's a good reason. # Once I have investigated sufficiently to satisfy ''my'' standards of evidence, I will post a preliminary determination for public feedback. # Anyone may state objections to this conclusion at any time, and I will either answer them or reconsider my conclusion, possibly re-opening the investigation. # Anyone may choose to go on record as supporting or opposing the conclusion. I will make these part of the public record to the best of my ability. #* Please note that opposition is not the same as stating an objection. I won't reconsider just because you oppose; you need to make an argument for why it is wrong. Please note that this is a good-faith process &ndash; i.e. one that depends on all participants being honest about their beliefs and intentions &ndash; and I will deal firmly with anyone I find to be acting otherwise. I have over a decade of experience spotting manipulation and evasion in online arguments. ==Footnotes== <references> <ref name=note1>This is a reference to the semi-capitalistic "marketplace of ideas" concept, with an ironic twist since capitalists don't seem to place much (if any) value on kindness (so their marketplaces tend to squash it out of existence) and since most Mastodonians are staunchly anti-marketist. That said, the idea of having numerous instances among which users may freely choose to invest various amounts of their time and energy actually ''is'' a kind of marketplace that's totally compatible with anarcho-capitalism &ndash; except I think we'd all tend to agree that basically having one person who gets to decide pretty much everything about how the system works is kind of iffy.</ref> <ref name=note2>This applies whether or not either user is on toot.cat, though obviously my actions will be more effective if one or the other is.</ref> <ref name=public>You could also approach me privately (DM or whatever) to discuss it before stating it publicly, or you might need me to try to keep your name out of the public process. I'm willing to consider intervening less publicly, but I suspect it will severely limit any good I might be able to do; if this emerges as a frequent need, I'll probably need to write up a separate process for dealing with it.</ref> <ref name=pip>It seems entirely appropriate that this abbreviates to PIP, which is also the name of our very messed-up cat ([https://toot.cat/@Pip Mastodon], [https://wiki.hypertwins.org/Pip HypertWiki]), since it is only invoked when a situation has become very messed-up. It is my hope that this process will soon become informally known as "requesting a Pip".</ref> <ref name=mastodm>Tentatively, this should be public but "unlisted" or "followers only". I may need to set up a dedicated investigation account so people can decide whether they want the investigation in their streams or not.</ref> </references> 1370855f907cd19de4fed13fbf87772cd350b54f 0 118 393 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/2018/04/07/sketching a code]] to [[Woozle/2018/04/07/sketching a code]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki #REDIRECT [[Woozle/2018/04/07/sketching a code]] f10ceb82a74a9a8e6eb6ba446f6dfa53d141529c 0 61 394 208 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/GlitchSoc]] to [[Woozle/GlitchSoc]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki ==Feature Requests== ===moderation panel=== * option to save a note when taking an action (right now, can only do these one at a time) * option to message the reporting user as part of the moderation action * should be a link to the problem user's stream * (large) retain deleted information somewhere, preferably in reinstateable form (don't destroy the evidence!) ===admin options=== * option for admins to get notifs (in web UI, not just email) of reports * option for admins to get notifs of new signups * somehow streamline the process so that multiple accounts can be silenced ** maybe a list, in admin, of accounts by signup date, with easy links to moderation panel *** preferably also a way to make notes on each user, visible only to other admins 3d7a5162c27bff1ed0a8f6158cbb54b7639f69cc 0 119 395 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/GlitchSoc]] to [[Woozle/GlitchSoc]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki #REDIRECT [[Woozle/GlitchSoc]] 92d3b7f6100b54de8fa9c79591dbe33101e7cc85 0 44 396 230 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/malusers]] to [[Woozle/malusers]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://lor.sh/@dump_stack dump_stack] | {{ls/domain|lor.sh}} | Mastodon | * '''2020-02-24''' [https://lor.sh/@dump_stack/103715838645490658] "people have anti-homeless attitudes because most of the time being homeless is a choice not a matter of chance." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li. '''Update 2018-10-07''': They have now been blocked after a report from a known user.</ref> </references> dad52bb7f102c4c2dc604ee3a18c5de4dcd55e3e 0 120 397 2022-11-12T15:14:55Z Woozle 1 Woozle moved page [[Pub/user/woozle/malusers]] to [[Woozle/malusers]]: eliminating "pub", and also "user" subfolder wikitext text/x-wiki #REDIRECT [[Woozle/malusers]] 71f50f59cb52012e784f2b13430e96c30d34048f 0 55 400 269 2022-11-12T15:34:17Z Woozle 1 Woozle moved page [[Pub/toot.cat/blocks/domain]] to [[Toot.cat/blocks/domain]]: eliminating "pub" wikitext text/x-wiki [[File:2021-01-07.screen.See what's happening - Pieville.png|thumb|why we blocked Pieville]] ==policy== The live list of active domain blocks is [https://toot.cat/about/more here] (scroll down) &ndash; but until recently, that didn't give a history or any discussion of reasoning, nor does Mastodon appear to log a time-stamp or admin name for domain blocks. Even now, it doesn't allow uploading of media or provide a way to allow more extensive discussion. We therefore have to keep a manual log if we want that information recorded in a manageable way. ==pages== * [[/logged]]: blocks enacted since we started keeping records * [[/legacy]]: blocks enacted before that ==blocks rescinded== * '''2020-07-22''' {{l/pub|inex.rocks}} * '''2019-12-30''' ([https://toot.cat/@news/103398519871689086 post]): After discussion among the admin team, we're removing silence from {{ls/domain|social.tchncs.de}} because it was hindering interaction in a [https://social.tchncs.de/@jookia/103393218723084741 useful thread], and nobody on the admin team knows/remembers why it was originally silenced. * '''2019-12-29''' ([https://toot.cat/@news/103393132862935518 post]) 75965e82f523ad7ba45a1bad200d8b51e318f581 0 121 401 2022-11-12T15:34:17Z Woozle 1 Woozle moved page [[Pub/toot.cat/blocks/domain]] to [[Toot.cat/blocks/domain]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat/blocks/domain]] d87ff79e3d4a685b9b788ff52a2aa2505db5e488 0 70 402 257 2022-11-12T15:34:17Z Woozle 1 Woozle moved page [[Pub/toot.cat/blocks/domain/legacy]] to [[Toot.cat/blocks/domain/legacy]]: eliminating "pub" wikitext text/x-wiki * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 45f78f46dd6994267a5d6ccfbaac8e6489cb707a 0 122 403 2022-11-12T15:34:17Z Woozle 1 Woozle moved page [[Pub/toot.cat/blocks/domain/legacy]] to [[Toot.cat/blocks/domain/legacy]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat/blocks/domain/legacy]] 06672165c912ef885132bd9a3f7c11c524a89dc9 0 69 404 284 2022-11-12T15:34:17Z Woozle 1 Woozle moved page [[Pub/toot.cat/blocks/domain/logged]] to [[Toot.cat/blocks/domain/logged]]: eliminating "pub" wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ''see also the automated lists at https://toot.cat/about/more'' ==2022== * '''2022-05-06''' [https://shrike.club/about shrike.club]: death threat -- https://archive.ph/PetvA * '''2022-04-29''' [https://honkwerx.tech/wildgoose honkwerx.tech]: admin advocates anti-trans violence [https://honkwerx.tech/notice/AIx0k1iha00hAykXya][https://honkwerx.tech/notice/AIx0oxWYbi7DbvQAWu] ([[:File:2022-04-29 at 15-36-28.screen.wildgoose (@wildgoose@honkwerx.tech).png|screenshot]]) * '''2022-03-24''' [https://freeatlantis.com/about/more freeatlantis.com]: see [https://cwre.org/w/Woozle/2022/03/24 this CWRE post] ==2021== * '''2021-01-07''' Pieville (see [[:File:2021-01-07.screen.See what's happening - Pieville.png|this screenshot]]) * '''2021-01-06''' Liberdon, after discussion with user and a mod (also a [https://toot.cat/web/statuses/105504258670114486 poll]) ==2020== * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, TERFs ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc 9b928843d8fcbd33bbd435919b15689e76045065 0 123 405 2022-11-12T15:34:17Z Woozle 1 Woozle moved page [[Pub/toot.cat/blocks/domain/logged]] to [[Toot.cat/blocks/domain/logged]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat/blocks/domain/logged]] 402de5ad7d850316a5be04bf681ac3c92d5fcee0 0 65 406 222 2022-11-12T15:34:52Z Woozle 1 Woozle moved page [[Pub/toot.cat/CoJ]] to [[Toot.cat/CoJ]]: eliminating "pub" wikitext text/x-wiki =The TootCat Code of Justice= {{box/principles| : Words have consequences. : All accusations should be taken seriously. }} ==License== This CoJ is basically an ''idea'', and as such cannot be legally protected from re-use. In case there is any ambiguity, however, we release the text on this page into the public domain. Other instances may adopt this, modify it, or (it shouldn't need to be said) ignore it completely; I'm content to let the marketplace of kindness<ref name=note1 /> decide whether such a thing is necessary or not, and to let the process of considered discussion refine it as needed. {{box/principles| : No accusation should be accepted as truth unless the evidence supports it. : A lie often contains just enough truth to make it plausible. : Both accusers and accused may need some protection. }} ==Status== This proposal is being posted by Woozle (TootCat &uuml;berwensch) and has not yet been reviewed for acceptance by our admins or users. Prior agreement with these terms will not, unlike with a CoC, be required for usage of TC; I will just want to make sure that everyone is aware of the process we intend to follow in the event of a dispute. This draft of the proposal also leaves a lot of ground uncovered, and I hope to address at least some of that before publicizing it further. [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 22:14, 26 December 2019 (UTC) ==Public Intervention Process<ref name=pip />== '''If you have a grievance against another user'''<ref name=note2 /> and would like me (as sysop of this instance) to do something about it: # "@" me (@woozle@toot.cat) with a public<ref name=public /> toot stating the nature of the problem and that you are requesting an Intervention. #* The primary types of problem I expect to be addressing are: (a) someone has abused you, or (b) someone has falsely accused you of abuse &ndash; but others may emerge. # This means I have your permission to investigate the situation and publicly post my findings on Mew (this wiki). #* I will probably need to ask a lot of nosy questions, both to you and the other parties involved. Let me know if you anticipate any problems with this. #* These discussions should take place on Mastodon<ref name=mastodm /> so as to be part of the public record, though I can make exceptions if there's a good reason. # Once I have investigated sufficiently to satisfy ''my'' standards of evidence, I will post a preliminary determination for public feedback. # Anyone may state objections to this conclusion at any time, and I will either answer them or reconsider my conclusion, possibly re-opening the investigation. # Anyone may choose to go on record as supporting or opposing the conclusion. I will make these part of the public record to the best of my ability. #* Please note that opposition is not the same as stating an objection. I won't reconsider just because you oppose; you need to make an argument for why it is wrong. {{box/principles| : I strive to evaluate first in terms of potential harm. : I strive not to decide until I have all the relevant facts. }} Please note that this is a good-faith process &ndash; i.e. one that depends on all participants being honest about their beliefs and intentions &ndash; and I will deal firmly with anyone I find to be acting otherwise. I have over a decade of experience spotting manipulation and evasion in online arguments. ==Related Pages== This idea was originally discussed and proposed on these pages: * {{l/pub|user/woozle/2018/04/05/justice in the fediverse}}: philosophical foundation * {{l/pub|user/woozle/2018/04/07/sketching a code}}: first draft of the process ==Footnotes== <references> <ref name=note1>This is a reference to the semi-capitalistic "marketplace of ideas" concept, with an ironic twist since capitalists don't seem to place much (if any) value on kindness (so their marketplaces tend to squash it out of existence) and since most Mastodonians are staunchly anti-marketist. That said, the idea of having numerous instances among which users may freely choose to invest various amounts of their time and energy actually ''is'' a kind of marketplace that's totally compatible with anarcho-capitalism &ndash; except I think we'd all tend to agree that basically having one person who gets to decide pretty much everything about how the system works is kind of iffy.</ref> <ref name=note2>This applies whether or not either user is on toot.cat, though obviously my actions will be more effective if one or the other is.</ref> <ref name=public>You could also approach me privately (DM or whatever) to discuss it before stating it publicly, or you might need me to try to keep your name out of the public process. I'm willing to consider intervening less publicly, but I suspect it will severely limit any good I might be able to do; if this emerges as a frequent need, I'll probably need to write up a separate process for dealing with it.</ref> <ref name=pip>It seems entirely appropriate that this abbreviates to PIP, which is also the name of our very messed-up cat ([https://toot.cat/@Pip Mastodon], [https://wiki.hypertwins.org/Pip HypertWiki]), since it is only invoked when a situation has become very messed-up. It is my hope that this process will soon become informally known as "requesting a Pip".</ref> <ref name=mastodm>Tentatively, this should be public but "unlisted" or "followers only". I may need to set up a dedicated investigation account so people can decide whether they want the investigation in their streams or not.</ref> </references> 4a48d4fd850a96bc70dea9bab1089d400a872d4d 0 124 407 2022-11-12T15:34:52Z Woozle 1 Woozle moved page [[Pub/toot.cat/CoJ]] to [[Toot.cat/CoJ]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat/CoJ]] d91937a22990107ad57d11cf50871163796d1e0c 0 62 408 236 2022-11-12T15:35:15Z Woozle 1 Woozle moved page [[Pub/toot.cat/CoC]] to [[Toot.cat/CoC]]: eliminating "pub" wikitext text/x-wiki =Code of Conduct= ==General== <p>As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users of the instance.</p> <p>We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.</p> <p>We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination.</p> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Accounts== Accounts that appear to be oriented towards promoting a business will be suspended without warning unless we have previously granted permission. We do wish to support individuals and cooperatively-organized groups engaged in activities to support themselves and their communities, but we also want to understand your goals and methods &ndash; and we will want to have some pretty solid communication around that established first. We will not accept paid advertising. We are all part of the human community, and we reject the idea that possession of money entitles the holder to obligations by others. ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> 39e32363e2233a3b5951736d0c786c45d2744826 0 125 409 2022-11-12T15:35:15Z Woozle 1 Woozle moved page [[Pub/toot.cat/CoC]] to [[Toot.cat/CoC]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat/CoC]] ee993b7f1cbc9b80744d6182aaa30368f257bb3d 0 48 410 272 2022-11-12T15:38:26Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Old Gnus== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) 4d71d9528760c3e6638048231aae575cce36a7e3 411 410 2022-11-12T15:38:59Z Woozle 1 Woozle moved page [[Pub/toot.cat]] to [[Toot.cat]]: eliminating "pub" wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Old Gnus== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) 4d71d9528760c3e6638048231aae575cce36a7e3 0 126 412 2022-11-12T15:38:59Z Woozle 1 Woozle moved page [[Pub/toot.cat]] to [[Toot.cat]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat]] 5c244992c79cbd6c958eec3d4392f47fe2f64ce4 0 57 413 197 2022-11-12T15:39:44Z Woozle 1 Woozle moved page [[Pub/text2toot]] to [[Text2toot]]: eliminating "pub" wikitext text/x-wiki ==About== '''text2toot''' is a connector which allows posting to Mastodon via texting from your phone. It was written by ash on 2019-01-25 and the source code is available [https://github.com/ashkitten/text2toot on GitHub]. It requires Twilio, or some other similar phone system back-end, to send and receive the texts. In theory, it can be used with any instance. More detailed setup instructions will be added as soon as I can. ==Syntax== * (no command, media attached) *: uploads media to instance for inclusion in next toot * clear_media *: clears currently pending attachments * post.visibility<nowiki>[[content warning]]</nowiki> post content *: sends toot, additionally including any pending media ** visibility is optional; defaults to global ** content warning is optional; defaults to none * register [instance] [token] *: sets current login * notify subscribe *: subscribes to mention notifications * notify unsubscribe *: unsubscribes from mention notifications fde16f3c356c5ddf1333802d164d44511197940b 415 413 2022-11-12T15:40:57Z Woozle 1 wikitext text/x-wiki ==About== '''text2toot''' is a connector which allows posting to Mastodon via texting from your phone. It was written by ash on 2019-01-25 and the source code is available [https://github.com/ashkitten/text2toot on GitHub]. It requires Twilio, or some other similar phone system back-end, to send and receive the texts. In theory, it can be used with any instance. We had it enabled on [[toot.cat]] for a few months, but there was very little interest and it became a technical liability. ==Syntax== * (no command, media attached) *: uploads media to instance for inclusion in next toot * clear_media *: clears currently pending attachments * post.visibility<nowiki>[[content warning]]</nowiki> post content *: sends toot, additionally including any pending media ** visibility is optional; defaults to global ** content warning is optional; defaults to none * register [instance] [token] *: sets current login * notify subscribe *: subscribes to mention notifications * notify unsubscribe *: unsubscribes from mention notifications 9922cd3be184bfb968cd6149a3b1e469d22c4923 416 415 2022-11-12T15:41:18Z Woozle 1 wikitext text/x-wiki [[category:software]] ==About== '''text2toot''' is a connector which allows posting to Mastodon via texting from your phone. It was written by ash on 2019-01-25 and the source code is available [https://github.com/ashkitten/text2toot on GitHub]. It requires Twilio, or some other similar phone system back-end, to send and receive the texts. In theory, it can be used with any instance. We had it enabled on [[toot.cat]] for a few months, but there was very little interest and it became a technical liability. ==Syntax== * (no command, media attached) *: uploads media to instance for inclusion in next toot * clear_media *: clears currently pending attachments * post.visibility<nowiki>[[content warning]]</nowiki> post content *: sends toot, additionally including any pending media ** visibility is optional; defaults to global ** content warning is optional; defaults to none * register [instance] [token] *: sets current login * notify subscribe *: subscribes to mention notifications * notify unsubscribe *: unsubscribes from mention notifications f75301231ebbda8218d3a6bd26a818454b828a83 0 127 414 2022-11-12T15:39:44Z Woozle 1 Woozle moved page [[Pub/text2toot]] to [[Text2toot]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Text2toot]] 5950950aa4866923a1702b5a15a6c2829ef9ce9e 0 26 417 83 2022-11-12T15:41:35Z Woozle 1 Woozle moved page [[Pub/switter.at]] to [[Switter.at]]: eliminating "pub" wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] {{seed}} ==Links== * https://dev.glitch.social/@cassolotl/99890887832152105 - screencap showing Switter reaching 50k+ users a462ce58d9a4d47e9f05c02caa13bb2d83405b05 419 417 2022-11-12T15:41:47Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] {{seed}} ==Links== * https://dev.glitch.social/@cassolotl/99890887832152105 - screencap showing Switter reaching 50k+ users b1d64c93bc95d5bee7960cf69924670d02e6a6ce 0 128 418 2022-11-12T15:41:35Z Woozle 1 Woozle moved page [[Pub/switter.at]] to [[Switter.at]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Switter.at]] 7c114d7931dd8df7cd2d8e29e4da0e043b86cc90 0 75 420 263 2022-11-12T15:42:09Z Woozle 1 Woozle moved page [[Pub/social.targaryen.house]] to [[Social.targaryen.house]]: eliminating "pub" wikitext text/x-wiki [[category:instances]] See [[issuepedia:social.targaryen.house]] -- should probably move that page here. a316adece2c27332b106699a752c1a4c9fbccc80 422 420 2022-11-12T15:42:23Z Woozle 1 wikitext text/x-wiki [[category:instance]] See [[issuepedia:social.targaryen.house]] -- should probably move that page here. b5acd5f31d9379feb4bbd979812c09ba0e2bf1db 0 129 421 2022-11-12T15:42:09Z Woozle 1 Woozle moved page [[Pub/social.targaryen.house]] to [[Social.targaryen.house]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Social.targaryen.house]] 332aee5eba38f7b136e1c1bdf4b417f3ca61af1f 0 39 423 103 2022-11-12T15:43:25Z Woozle 1 Woozle moved page [[Pub/mastodon.cloud]] to [[Mastodon.cloud]]: eliminating "pub" wikitext text/x-wiki [[category:instances]] [[category:Mastodon]] ==Contact== Sysop seems to be Valentin Ouvrard: * [https://twitter.com/Valentin_NC Twitter] * [https://www.patreon.com/ValentinOuvrard Patreon] ** [https://twitter.com/Woozalia/status/1002900363647832065 Woozle asks what's up] ==News== * '''2018-06-04''' Tweet: [https://mobile.twitter.com/Valentin_NC/status/1003528732223475717 "Yeah, I'm currently in migration to Japan datacenter, It take a while due of the instance size... We will back soon :)"] * '''2018-06-02''' [https://toot.cat/@RefurioAnachro/100134355499771070 A mastodon.cloud refugee reports] that the instance has been down for over a week. ==Archives== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about] 62c30a129126369f21e6930e658b7eb643739d8f 427 423 2022-11-12T15:44:59Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] ==Contact== Sysop seems to be Valentin Ouvrard: * [https://twitter.com/Valentin_NC Twitter] * [https://www.patreon.com/ValentinOuvrard Patreon] ** [https://twitter.com/Woozalia/status/1002900363647832065 Woozle asks what's up] ==News== * '''2018-06-04''' Tweet: [https://mobile.twitter.com/Valentin_NC/status/1003528732223475717 "Yeah, I'm currently in migration to Japan datacenter, It take a while due of the instance size... We will back soon :)"] * '''2018-06-02''' [https://toot.cat/@RefurioAnachro/100134355499771070 A mastodon.cloud refugee reports] that the instance has been down for over a week. ==Archives== * '''2018-04-12''' archive.org: [https://web.archive.org/web/20180412065239/https://mastodon.cloud/about mastodon.cloud/about] 1c0f3c57784ba93260e701108cca859744c2db42 0 130 424 2022-11-12T15:43:25Z Woozle 1 Woozle moved page [[Pub/mastodon.cloud]] to [[Mastodon.cloud]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Mastodon.cloud]] a2c1e3006276eaddd32e1623db67fb7275038cd8 14 36 425 86 2022-11-12T15:44:07Z Woozle 1 Woozle moved page [[Category:Instances]] to [[Category:Instance]] without leaving a redirect: categories should be singular wikitext text/x-wiki instances on the Mastodon fediverse cc559d5b53aee4627900da92dc7037d8e634c64e 0 48 426 411 2022-11-12T15:44:42Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Old Gnus== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) d89751712b539555f6c9d7755aeb08725db31f9f 0 68 428 262 2022-11-12T15:45:53Z Woozle 1 wikitext text/x-wiki [[category:instance]] ==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person): ===The negative=== The [https://toot.cat/@girl/104462394989007467 one lead I was able to get] on this domain said: * The main admin is known to follow people on domains that are often considered problematic, specifically [https://expired.mentality.rip/about expired.mentality.rip], [https://lor.sh/about/more" lor.sh], and the admin's own domain ([https://enigmatic.observer/about enigmatic.observer]). * The second admin is [https://udongein.xyz/naiji naiji@udongein.xyz], which is another often-blocked domain and a quick glance at that profile in early July apparently showed direct communications with users on {{ls/domain|neckbeard.xyz}}, freespeechextremist, kiwifarms, pl.smuglo.li and other frequently blocked domains. I don't know anything about neckbeard, but "free speech extremism" does tend to refer to a lot of very toxic forms of advocacy, and {{l/ip|kiwifarms}} is, from all reports, just plain evil. ===That said...=== Merely being willing to engage in dialogue with toxic people does not necessarily mean that one is toxic. I do not wish to promote a culture of fearing guilt-by-association. Additionally, I have no idea of the nature of the contact; was naiji interacting ''approvingly'' with those folks, or in an appropriately skeptical manner? Is it happening in a way that causes nastiness to populate the timeline, if I federate with it? Ultimately, I think that should be up to my userbase to decide -- and this time, if there are incidents, we will document them for future reference. At this point, due primarily to a lack of documentation of what incident(s) triggered the current block: I've reversed it (with this page as a log of my reasoning), and we will just watch carefully for any future issues with it. ==Footnotes== <references> <ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 reply] to [https://enigmatic.observer/users/inex Inex Code]</ref> </references> e9d80b3171932ca3884e98d3a4c58881126a8481 429 428 2022-11-12T15:46:11Z Woozle 1 Woozle moved page [[Pub/inex.rocks]] to [[Inex.rocks]]: eliminating "pub" wikitext text/x-wiki [[category:instance]] ==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person): ===The negative=== The [https://toot.cat/@girl/104462394989007467 one lead I was able to get] on this domain said: * The main admin is known to follow people on domains that are often considered problematic, specifically [https://expired.mentality.rip/about expired.mentality.rip], [https://lor.sh/about/more" lor.sh], and the admin's own domain ([https://enigmatic.observer/about enigmatic.observer]). * The second admin is [https://udongein.xyz/naiji naiji@udongein.xyz], which is another often-blocked domain and a quick glance at that profile in early July apparently showed direct communications with users on {{ls/domain|neckbeard.xyz}}, freespeechextremist, kiwifarms, pl.smuglo.li and other frequently blocked domains. I don't know anything about neckbeard, but "free speech extremism" does tend to refer to a lot of very toxic forms of advocacy, and {{l/ip|kiwifarms}} is, from all reports, just plain evil. ===That said...=== Merely being willing to engage in dialogue with toxic people does not necessarily mean that one is toxic. I do not wish to promote a culture of fearing guilt-by-association. Additionally, I have no idea of the nature of the contact; was naiji interacting ''approvingly'' with those folks, or in an appropriately skeptical manner? Is it happening in a way that causes nastiness to populate the timeline, if I federate with it? Ultimately, I think that should be up to my userbase to decide -- and this time, if there are incidents, we will document them for future reference. At this point, due primarily to a lack of documentation of what incident(s) triggered the current block: I've reversed it (with this page as a log of my reasoning), and we will just watch carefully for any future issues with it. ==Footnotes== <references> <ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 reply] to [https://enigmatic.observer/users/inex Inex Code]</ref> </references> e9d80b3171932ca3884e98d3a4c58881126a8481 0 131 430 2022-11-12T15:46:11Z Woozle 1 Woozle moved page [[Pub/inex.rocks]] to [[Inex.rocks]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Inex.rocks]] 253dbdcd3617ea878586b01664119ec74c167ca0 0 58 431 198 2022-11-12T15:46:45Z Woozle 1 Woozle moved page [[Pub/hackers.town]] to [[Hackers.town]]: eliminating "pub" wikitext text/x-wiki [[category:instances]] May be run by an FBI informant? See [https://dragon.style/@packbat/101694219419341628 this]. e275bfc3da82717cd4ca1dd7de60a8cc45cb347e 433 431 2022-11-12T15:46:58Z Woozle 1 wikitext text/x-wiki [[category:instance]] May be run by an FBI informant? See [https://dragon.style/@packbat/101694219419341628 this]. 2ec7f1e5629b097123f1c3357aa27eacab31c719 0 132 432 2022-11-12T15:46:45Z Woozle 1 Woozle moved page [[Pub/hackers.town]] to [[Hackers.town]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Hackers.town]] ca8f56dedd62a29015280d066f5a1f8ee417fad3 0 77 434 286 2022-11-12T15:47:18Z Woozle 1 Woozle moved page [[Pub/email confirmation]] to [[Email confirmation]]: eliminating "pub" wikitext text/x-wiki If you're having trouble receiving email confirmation: * Microsoft's email servers tend to block messages from our servers. This includes '''HotMail''', '''Outlook.com''', and even some university mail systems. Getting the blocks removed and keeping them removed takes more time-resources than we currently have available &ndash; and, lately, seems to be basically impossible: [https://answers.microsoft.com/en-us/outlook_com/forum/all/hotmailoutlook-block-list-s3140-blocks-all-new/699f3a56-406e-4804-97e2-cbe23b9bb01c this appears to be a Microsoft problem, not a technical issue on our end]. If you sign up using an email at one of these services, you will not be able to complete the process &ndash; so obviously we recommend against using them. (Microsoft seems to be keen on basically de-federating from the emailverse.) * If you are having trouble receiving the sign-up confirmation email on a ''non''-Microsoft email account, please email [mailto:tootcat.{{CURRENTTIMESTAMP}}@wooz.dev tootcat.{{CURRENTTIMESTAMP}}@wooz.dev] to let me know. ''&ndash; [[User:Woozle|Woozle]] ([[User talk:Woozle|talk]]) 14:05, 27 October 2021 (UTC)'' ==Related== * '''2022-05-06''' @woozle: [https://toot.cat/@woozle/108255493723637622 GMail has suddenly started bouncing our emails...]: I haven't confirmed whether toot.cat's emails are affected, but GMail is definitely blocking messages sent from one of our other servers (both are on DigitalOcean), so it seems likely. *** '''2022-05-07''' UPDATE: No, it was just cloud1. The error message from Google was ''completely'' misleading; the problem was that the server had been redlisted by Spamhaus, and I was able to get it de-listed. (No reason was given for why it got redlisted.) * '''2022-04-28''' @woozle: [https://toot.cat/@woozle/108210129980886571 I need to figure out what to do about people signing up for #TootCat (with) #Microsoft email addresses...] * '''2021-10-27''' @woozle: [https://toot.cat/@woozle/107173957644432715 ... I need to put in a link to our new warning about Microsoft's email servers being chronically rude to me. ...] f6da0aaba8ad07154e68575ec4911683a9a8f2d4 0 133 435 2022-11-12T15:47:18Z Woozle 1 Woozle moved page [[Pub/email confirmation]] to [[Email confirmation]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Email confirmation]] 9011f9aaaf31bf97ced4b96f4d5b8762d069961e 0 18 436 184 2022-11-12T15:48:16Z Woozle 1 Woozle moved page [[Pub/witches.town]] to [[Witches.town]]: eliminating "pub" wikitext text/x-wiki [[category:Mastodon]] [[category:instances]] [[category:defunct]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces; see {{l/pub|witches}} for a list. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 454a905562c8518cf18a462c97cbb1c684573ea1 438 436 2022-11-12T15:48:41Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:defunct]] [[File:Screenshot-2018-4-2 Personnes suivies par The Supreme Witch.crop.png|thumb|the witches.town admin team]] [[File:B03116fbd6f7793f.png|thumb|migration survey results]] '''witches.town''' (WT) was a Mastodon instance that went offline on 2018-04-30 for reasons. WT had been a somewhat quirky place &ndash; e.g. the limit for toots is 666 characters rather than the standard 500, and a pentagram symbol was apparently given to users with exactly 666 followers &ndash; with a very loyal membership. ==Shutdown== @TheSupreme@witches.town, sysop of the instance, [https://toot.cat/web/statuses/99790692143728971 announced] on 2018-04-02 that she will be shutting it down on 2018-04-30 &ndash; closely followed by a [https://toot.cat/web/statuses/99790761792891193 later toot] noting that she was unwilling to let someone else take over the service (thus contradicting the "burnout" explanation), but without saying why. There had previously been a [https://toot.cat/web/statuses/99757948365320502 surprise takeover on March 27] in which @TheSupreme removed all the other sysops, giving the following [https://toot.cat/web/statuses/99760206833368349 explanation]: <blockquote>Half of the moderation team was thinking of leaving and was not doing much anyway, the other half was getting endlessly stuck in "non-decision wait and see mode". This alone let some heavy shitstorms live their lives. The thing that made me dissolve the team yesterday was a decision made by an admin to suspend the account of a trans woman based on an old smear campaign pushed by 4 chan with the subsequent support of the majority of the team. Giving credit to 4chan, the gamergate and the alt-right is never ok. So I stepped in. </blockquote> The code customizations used by WT are currently still available [https://github.com/WitchesTown/mastodon on GitHub]. The loss of witches.town led directly to interest in creating and supporting more witch-friendly spaces; see {{l/pub|witches}} for a list. ==Official Toots== ''all times are EDST'' * '''2018-04-02''' ** '''12:05''' [https://witches.town/@TheSupreme/99790692010452099 That's it. I'm burnt out. I terminated the server lease.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ** '''10:03''' [https://ltch.fr/@Alda/99790211177963067 Reaaaally hot take about transidentity. Be careful, you're about to get yourself burned.] ([https://toot.cat/web/statuses/99790211582721073 cache]) *** @Alda@itch.fr is apparently the main account for @TheSupreme@witches.town (see 03-27 toot). ** '''2018-03-27''' [https://witches.town/@TheSupreme/99757948217405250 I am taking back the management of WitchesTown.] ([https://toot.cat/web/statuses/99757948365320502 cache]) ==Related== * '''2018-04-30''' [https://dev.glitch.social/@cassolotl/99947935739267460 Migration survey results] 89eba942e23ccf57849584721edfd0e6efe7f85b 0 134 437 2022-11-12T15:48:16Z Woozle 1 Woozle moved page [[Pub/witches.town]] to [[Witches.town]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Witches.town]] 26ff9b23dd1541ffee65c4d8e9f70eb0f8df24c3 0 54 439 229 2022-11-12T15:49:02Z Woozle 1 Woozle moved page [[Pub/witches]] to [[Witches]]: eliminating "pub" wikitext text/x-wiki [[category:instances]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} * {{ls/domain|witches.live}} "a mastodon instance for witches" ** [https://fedi.lynnesbian.space/@lynnesbian/101883861030638834 2019-04-07]: problem with the admin? it sounds like partly a misunderstanding, though Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} 7b51cbb634a8a5f4d27f3927505ec83430966c88 441 439 2022-11-12T15:50:00Z Woozle 1 wikitext text/x-wiki [[category:instance/topic]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * {{ls/domain|witchcraft.cafe}} * {{ls/domain|witches.live}} "a mastodon instance for witches" ** [https://fedi.lynnesbian.space/@lynnesbian/101883861030638834 2019-04-07]: problem with the admin? it sounds like partly a misunderstanding, though Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} Defunct: * [[witches.town]] b3d8ceef5c1932f2c52080f0fadbc0d8a9df49ee 447 441 2022-11-12T15:53:58Z Woozle 1 wikitext text/x-wiki [[category:instance/topic]] ==Mastodon Instances== Witch-related: * {{ls/domain|occult.camp}} "aethestically witchy" * {{ls/domain|pentacl.es}} * [[witchcraft.cafe]] * {{ls/domain|witches.live}} "a mastodon instance for witches" ** [https://fedi.lynnesbian.space/@lynnesbian/101883861030638834 2019-04-07]: problem with the admin? it sounds like partly a misunderstanding, though Related, but not expressly witchy: * {{ls/domain|eldritch.cafe}} (mainly French) Possibly witchy, but not available for registration: * {{ls/domain|cybrewitch.es}} Defunct: * [[witches.town]] 72912013eabc5aeb1dd0e726763e0002dc04158d 0 135 440 2022-11-12T15:49:03Z Woozle 1 Woozle moved page [[Pub/witches]] to [[Witches]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Witches]] a3138f56a7479ef0f49a3c8f51854acb8f8e5460 14 136 442 2022-11-12T15:51:18Z Woozle 1 Created page with "{{fmt/title|topics around which some instances are focused}}" wikitext text/x-wiki {{fmt/title|topics around which some instances are focused}} 7b00a3447354c2bb95430a09eed4d1bb76165aa3 0 52 443 383 2022-11-12T15:52:31Z Woozle 1 wikitext text/x-wiki [[category:instance/topic]] [[File:B2b7aef4d7e11ff5.png|thumb|a new user reacts to Mastodon ([https://masto.donte.com.br/@renatolond/100564715379692917 via])]] =Cat Directory= Since [[toot.cat]] is nominally a cat-related instance, we thought we should start keeping a list of cat-related things on the fediverse as a handy reference. ==Tooting Cat Accounts on TootCat== * [https://toot.cat/@booseandpi caboose & penelope] * [https://toot.cat/@eddy Eddy] (a smol orange tabby girl cat) * [https://toot.cat/@este este] (an angry bengal) * [https://toot.cat/@kestra Kestra], who is Very Disappointed in {{l/pub/user|woozle}} and [https://toot.cat/@Harena Harena] * [https://toot.cat/@Lady Lady] (a bicolor medium-length street cat with feline herpes) * [https://toot.cat/@luce luce] * [https://toot.cat/@lugebootie lugebootie] (Finnegan and Oliver) * [https://toot.cat/@meowra meowra] (Onyx and Rudy) * [https://toot.cat/@mowe mowe] * [https://toot.cat/@Pip Pip]: a dufus belonging to {{l/pub/user|woozle}} * [https://toot.cat/@rarity rarity] * [https://toot.cat/@salemramona Salem & Ramona] * [https://toot.cat/@Sargoth Sargoth (cat aspect)] ===cat people=== * [https://toot.cat/@KittyMinT mint] "im mint and im like cats." * [https://toot.cat/@oscelot Oscelot] -- [https://toot.cat/@oscelot/100585328496929184 claims] not to be cat-related, but profile also says "cat". We are confused. ==Other Items== * {{ls/domain|kitty.town}} (Mastodon instance): domain of the most excellent Ginny McQueen ** {{l/mastodon|cats|kitty.town}} * [https://cybre.space/@netkitty kitten.exe] (Mastodon account) ** ([https://meow.social/@netkitty old account]) * {{l/hashtag|cats}} ==Not Cat-Focused== * {{ls/domain|meow.social}} (Mastodon instance) - "focused around the furry community" 20d86652c6bdad8731f03f1d2581b716daf66723 0 35 444 90 2022-11-12T15:53:00Z Woozle 1 Woozle moved page [[Pub/witchcraft.cafe]] to [[Witchcraft.cafe]]: eliminating "pub" wikitext text/x-wiki [[category:instances]] ==Notes== * https://mastodon.starrevolution.org/@Laurelai/100080256575111626 ** https://mastodon.starrevolution.org/@Laurelai/100080413877659466 8210ff9cc2306965f9d5c6e4f8e8d21c5be5b856 446 444 2022-11-12T15:53:19Z Woozle 1 wikitext text/x-wiki [[category:instance]] ==Notes== * https://mastodon.starrevolution.org/@Laurelai/100080256575111626 ** https://mastodon.starrevolution.org/@Laurelai/100080413877659466 bf5f3858e5454042cc002a6605d414ef362861e2 448 446 2022-11-12T15:54:54Z Woozle 1 wikitext text/x-wiki [[category:instance]] * '''site''': {{ls/domain|witchcraft.cafe}} (could not access on 2022-11-12) ==Notes== * https://mastodon.starrevolution.org/@Laurelai/100080256575111626 ** https://mastodon.starrevolution.org/@Laurelai/100080413877659466 b8f7c5540cba35647faa87e2190c5c6803c51f72 0 137 445 2022-11-12T15:53:00Z Woozle 1 Woozle moved page [[Pub/witchcraft.cafe]] to [[Witchcraft.cafe]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Witchcraft.cafe]] 2369835a3c82315c045ad2832cfb6cedcf4f41aa 0 66 449 271 2022-11-12T15:55:15Z Woozle 1 Woozle moved page [[Pub/toot.cat/guidelines]] to [[Toot.cat/guidelines]]: eliminating "pub" wikitext text/x-wiki ==Red Flags== TootCat will block individuals and instances who persistently raise these flags: * '''Punching down''': it's not okay to punch down, and it's okay to call out people who are doing it. ** In general, "punching down" means criticizing people who are underprivileged or have less power than you. ** Examples: *** making fun of nontraditional pronouns [https://social.panthermodern.net/@0x00/103754842757342400] *** deliberately misgendering someone, especially a trans person * '''Using "free speech" as an excuse''' ({{l/ip|free speech trolling}}) ** {{l/ip|Freedom of speech}} just means ''the government'' can't stop you from saying things. ** It does not mean freedom from consequences if you say something obnoxious or hurtful. ** It does not mean that any private venue is required to give you a platform. ** One opinion is ''not'' as good/valid as any other ''if one of them is harmful''. *** Inaccuracy of factual details is often (but not always) a cause of harm, as it can lead to maltreatment of others. [[issuepedia:Truth/evidenced|Truth]] matters. 2f453a26e1dbc4627e0241058d770ed2869d54eb 0 138 450 2022-11-12T15:55:15Z Woozle 1 Woozle moved page [[Pub/toot.cat/guidelines]] to [[Toot.cat/guidelines]]: eliminating "pub" wikitext text/x-wiki #REDIRECT [[Toot.cat/guidelines]] ac501015200f5115f6316ee8c8f7f572d1c62828 0 1 451 309 2022-11-12T16:03:06Z Woozle 1 /* Public Pages */ wikitext text/x-wiki __NOTOC__ <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Site Status== {{i/val|status|page=toot.cat}} ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: Woozle's public pages ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 07eff8fad1f1dfaeab744fa35c76a9f5ec25238a 460 451 2022-11-16T00:48:43Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: Woozle's public pages ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Site News== * '''{{l/pub|2020-03-31}}''' site going down for an upgrade * '''2018-10-11''' We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> e6eb8cffca398bee1c5467cee97e3ba40d0ba27a 461 460 2022-11-16T00:49:48Z Woozle 1 /* Site News */ wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: Woozle's public pages ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Site News== * '''[[2020-03-31]]''' site going down for an upgrade * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 0c7e91f572b523dd4b8faa9a76870d200c8bb5e8 0 89 452 354 2022-11-12T16:05:05Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-12 11:03EST''' toot.cat is maybe still a bit slow and cranky.|The queue is shorter. Uploads are working better but not always. We're still working on the favicons and CPU optimizations.}} accb55e90fc2ce33cc5b27f137954d86ec1abe87 455 452 2022-11-14T17:38:09Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-14 12:36 EST''' toot.cat is mostly okay.|The peak queue continues to get shorter. Uploads seem snappy most of the time. We're still working on the favicons and CPU optimizations.}} 502cb667d46c0ad82181e96ad3cb553c6dace2c0 458 455 2022-11-15T22:54:54Z Woozle 1 wikitext text/x-wiki {{hdr/notice/error|'''2022-11-15 17:52 EST''' toot.cat is substantially borked.|Sidekiq seems to be running, systemctl gives green lights, but we have a failephant. Working on it, of course. We apologize for the mess.}} 95a9026dd81cf0e4efa317da540b1272e82cd2cc 459 458 2022-11-16T00:33:02Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2022-11-15 19:31 EST''' We have successfully reverted to the earlier, mostly-unborked TootCat.|Further diagnosis is in progress; we have a couple of paths forward.}} 9ad1c59d962131be2826ae1144d702c95e3b1dd4 0 139 453 2022-11-14T01:41:49Z Woozle 1 Created page with "[[category:instance]] ==Notes== * '''2018-03-04''' [https://medium.com/we-distribute/hiveway-io-shamelessly-rips-off-of-mastodon-and-slaps-a-blockchain-on-top-for-some-reason-..." wikitext text/x-wiki [[category:instance]] ==Notes== * '''2018-03-04''' [https://medium.com/we-distribute/hiveway-io-shamelessly-rips-off-of-mastodon-and-slaps-a-blockchain-on-top-for-some-reason-57b7aba3e84f Hiveway.io forks Mastodon and slaps a blockchain on top, for some reason] ([https://beach.city/@vantablack/109339035732913060 h/t]) 8d1b703fb4089972c2721a2d6de546e4c5fe6019 10 140 454 2022-11-14T17:35:22Z Woozle 1 Created page with "'''&#171;'''<span style="font-family:serif; color:#480;">{{{1}}}</span>'''&#187;'''" wikitext text/x-wiki '''&#171;'''<span style="font-family:serif; color:#480;">{{{1}}}</span>'''&#187;''' e62f59a2af63091f591ab3069b96f19029684fd0 0 141 456 2022-11-14T17:42:20Z Woozle 1 Created page with "{{page/date}} * '''previous page''': [[../11|Nov. 11]] ==Notes== * [https://social.tranarchy.fish/@autumnull/statuses/01GHV4P8M8M3WFK3C4J4XH5SN4 warning about far-right transp..." wikitext text/x-wiki {{page/date}} * '''previous page''': [[../11|Nov. 11]] ==Notes== * [https://social.tranarchy.fish/@autumnull/statuses/01GHV4P8M8M3WFK3C4J4XH5SN4 warning about far-right transphobe on fedi]: {{fmt/quote|suzanne_moore at [[toot.community|toot dot community]], one of the most prominent UK press transphobes, working for far-right <s>Murdoch</s> Barclay Brother rag the ''Daily Telegraph''. her twitter profile confirms it's really her.}} ** [https://mspsocial.net/@lawremipsum/109341923369326570 observation of a pattern we may have to watch out for] d9a4f0b8244d74dc123f662e7632e5878004b61f 10 142 457 2022-11-15T22:54:20Z Woozle 1 Created page with "{{hdr/notice|{{{1}}}|{{{2|}}}|color=#f88}}" wikitext text/x-wiki {{hdr/notice|{{{1}}}|{{{2|}}}|color=#f88}} dbbf35f16f023054913894496307adc3f94a86df 10 87 462 319 2022-11-16T15:29:43Z Woozle 1 option to add nav info below yesterday/tomorrow navbox wikitext text/x-wiki {{c/date|{{PAGENAME}}}} [[category:time]] [[category:date]] {{fmt/title| {{#time: l, F j, Y | {{PAGENAME}}}} {{#time: (#z) | {{PAGENAME}} + 1 day}} }} <table width=100% style="border-bottom: 1px solid green;"><tr><td valign=bottom> <table width=100%><tr><td valign=top> <table class=wikitable><tr> <td> [[ {{#time: Y/m/d | {{PAGENAME}} - 1 day}} | {{#time: l | {{PAGENAME}} - 1 day}} ]] </td> <td> '''{{#time: l | {{PAGENAME}}}}''' </td> <td> [[ {{#time: Y/m/d | {{PAGENAME}} + 1 day}} | {{#time: l | {{PAGENAME}} + 1 day}} ]] </td> </tr></table> {{{nav|}}} </td><td> {{i/val|status|page=toot.cat}} </td></tr></table> 7049e69374f0fb35a0546da3d312808b625b4c6c 0 141 463 456 2022-11-16T15:31:47Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[../11|Nov. 11]] .. today .. [[../16|Nov. 16]] }} ==Notes== * [https://social.tranarchy.fish/@autumnull/statuses/01GHV4P8M8M3WFK3C4J4XH5SN4 warning about far-right transphobe on fedi]: {{fmt/quote|suzanne_moore at [[toot.community|toot dot community]], one of the most prominent UK press transphobes, working for far-right <s>Murdoch</s> Barclay Brother rag the ''Daily Telegraph''. her twitter profile confirms it's really her.}} ** [https://mspsocial.net/@lawremipsum/109341923369326570 observation of a pattern we may have to watch out for] 9badf4edb30b877b2e137bfc6ad80549312f8aa5 465 463 2022-11-16T15:35:05Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[../11|prev]] .. [[../14|today]] .. [[../16|next]] }} ==Notes== * [https://social.tranarchy.fish/@autumnull/statuses/01GHV4P8M8M3WFK3C4J4XH5SN4 warning about far-right transphobe on fedi]: {{fmt/quote|suzanne_moore at [[toot.community|toot dot community]], one of the most prominent UK press transphobes, working for far-right <s>Murdoch</s> Barclay Brother rag the ''Daily Telegraph''. her twitter profile confirms it's really her.}} ** [https://mspsocial.net/@lawremipsum/109341923369326570 observation of a pattern we may have to watch out for] 1c6fb5d08d6787c488ac4464fc290e5eb0c04868 0 143 464 2022-11-16T15:34:09Z Woozle 1 Created page with "{{page/date|nav=[[../14|Nov. 14]] .. [[../16|today]] .. (nothing newer yet) }}" wikitext text/x-wiki {{page/date|nav=[[../14|Nov. 14]] .. [[../16|today]] .. (nothing newer yet) }} 289b763c93defada3cb26e640b94c2b079c0f294 467 464 2022-11-16T15:41:09Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[../14|prev]] .. [[../16|today]] .. (no next yet) }} ==Upgrade Plan== There's a bit of time-pressure to get the upgrade working because of a [https://portswigger.net/research/stealing-passwords-from-infosec-mastodon-without-bypassing-csp security vulnerability] in the RC version that just happened to be what we upgraded to, but I also don't want to crash the server again (as happened yesterday). The team agrees that we need a test-deployment process. The broad outlines I've worked out: * live image the TC server * spin up a copy, and reconfig it to be dev.toot.cat * make sure it's running ok as-is (data might have gotten munged by being live-imaged; if so, can do a pg data export/import) * reconfig Nix to target dev.TC * run the upgrade * look at dev.TC and see if everything runs ok Preparation needed before this can work: * modify Nix scripts so they can switch target servers easily * figure out what changes need to be made to the server image in order to run properly as dev.TC instead of TC * write a subscript to automate those changes Meanwhile, I need to do a little research to figure out how to nicely ask {{l/htyp|Git}} to compare two existing commits for me. (All of the relevant commits are {{l/htyp|Git/tag|tagged}}, fortunately.) 68b5730c823706ca044bf40a1b392fb70e019e8d 488 467 2022-11-18T15:54:04Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[../14|prev]] .. [[../16|today]] .. [[../17|next]] }} ==Upgrade Plan== There's a bit of time-pressure to get the upgrade working because of a [https://portswigger.net/research/stealing-passwords-from-infosec-mastodon-without-bypassing-csp security vulnerability] in the RC version that just happened to be what we upgraded to, but I also don't want to crash the server again (as happened yesterday). The team agrees that we need a test-deployment process. The broad outlines I've worked out: * live image the TC server * spin up a copy, and reconfig it to be dev.toot.cat * make sure it's running ok as-is (data might have gotten munged by being live-imaged; if so, can do a pg data export/import) * reconfig Nix to target dev.TC * run the upgrade * look at dev.TC and see if everything runs ok Preparation needed before this can work: * modify Nix scripts so they can switch target servers easily * figure out what changes need to be made to the server image in order to run properly as dev.TC instead of TC * write a subscript to automate those changes Meanwhile, I need to do a little research to figure out how to nicely ask {{l/htyp|Git}} to compare two existing commits for me. (All of the relevant commits are {{l/htyp|Git/tag|tagged}}, fortunately.) 29a9931687873f8ac6306de876141880c4d1950b 0 103 466 355 2022-11-16T15:36:08Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[../10|prev]] .. [[../11|today]] .. [[../14|next]] }} * '''14:53 EST''' [https://toot.cat/@woozle/109326921792556208 post about Masto favicons and documentation] ...and I'm still not at all sure {where in the Nix config} the load-optimizations settings are, but I need to mostly break from working on this for a day or so. A thing for me to look at later: [https://github.com/vivlim/nixpkgs/blob/tootcat/nixos/modules/services/web-apps/mastodon.nix mastodon.nix] is where the stuff defined in configuration.nix gets built into the actual Mastodon config (presumably including the various standard Masto config files), according to Nixpert. e06a6fc403ef9ab56579cc82d4ef6a6b998530f9 0 144 468 2022-11-18T01:19:08Z Woozle 1 Created page with "==email from Jeffrey Freeman== <blockquote> Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our p..." wikitext text/x-wiki ==email from Jeffrey Freeman== <blockquote> Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote> <b/lockquote> 659616222006ae4a1a118d989de0237ce55ef00b 477 468 2022-11-18T01:35:04Z Woozle 1 screenshots wikitext text/x-wiki ==email from Jeffrey Freeman== [[File:2022-11.screen.qoto.1.png|thumb|a QOTO user mentions the tool]] [[File:2022-11.screen.qoto.2.png|thumb|JF plans to email the admins of instances that have defederated from QOTO]] [[File:KF.fedi-block.screen.png|thumb|screenshot of the tool in question, clearly showing its KF provenance]] <blockquote> Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote> <b/lockquote> f8e79d3df2f1d69bd5b72fc9c58eb7d5bfa4b7b1 478 477 2022-11-18T01:36:19Z Woozle 1 wikitext text/x-wiki ==email from Jeffrey Freeman== [[File:2022-11.screen.qoto.1.png|thumb|a QOTO user mentions the tool]] [[File:2022-11.screen.qoto.2.png|thumb|JF plans to email the admins of instances that have defederated from QOTO]] [[File:KF.fedi-block.screen.png|thumb|screenshot of the tool in question, clearly showing its KF provenance]] <blockquote> Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: : 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. : 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). : 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote> <b/lockquote> 6bd605ce35b678be0a80421e47028fcdc7608b38 479 478 2022-11-18T01:52:47Z Woozle 1 wikitext text/x-wiki Background: we blocked qoto.org a week or three ago for the following reason: : "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. [2022-11-12] changing from block to silence by user request; see https://toot.cat/@woozle/109331146818085671 We received this email today. It partly seems reasonable, and partly sets off a few flags, and... I need to think about it and get community feedback. ==email from Jeffrey Freeman== [[File:2022-11.screen.qoto.1.png|thumb|a QOTO user mentions the tool]] [[File:2022-11.screen.qoto.2.png|thumb|JF plans to email the admins of instances that have defederated from QOTO]] [[File:KF.fedi-block.screen.png|thumb|screenshot of the tool in question, clearly showing its KF provenance]] <blockquote> Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: : 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. : 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). : 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote> <b/lockquote> 3063b87e702a83f199128d0a59c672fd863e1e50 480 479 2022-11-18T01:56:09Z Woozle 1 wikitext text/x-wiki Background: we blocked qoto.org a week or three ago for the following reason: : "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. [2022-11-12] changing from block to silence by user request; see https://toot.cat/@woozle/109331146818085671 We received this email today. It partly seems reasonable, and partly sets off a few flags. Basically, the admin used a tool to identify other instances that were blocking QOTO, and sent them all emails (probably this one, verbatim). The list of email addresses was apparently assembled manually, and his argument seems reasonable, but the tool in question originally comes from the {{l/ip|Kiwi Farms}} online terrorism organization (thankfully now defunct). ==email from Jeffrey Freeman== [[File:2022-11.screen.qoto.1.png|thumb|a QOTO user mentions the tool]] [[File:2022-11.screen.qoto.2.png|thumb|JF plans to email the admins of instances that have defederated from QOTO]] [[File:KF.fedi-block.screen.png|thumb|screenshot of the tool in question, clearly showing its KF provenance]] <blockquote> Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: : 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. : 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). : 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote> <b/lockquote> c7550123dde2c996f29f06ea5a09a5fec6e3944a 487 480 2022-11-18T15:12:40Z Woozle 1 wikitext text/x-wiki '''Background''': we blocked [[qoto.org]] a week or three ago for the following reason: : "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. [2022-11-12] changing from block to silence by user request; see https://toot.cat/@woozle/109331146818085671 We received an email today from Jeffrey Freeman, presumably the owner. Investigation by our admins found that basically, the admin used a tool to identify other instances that were blocking QOTO, and sent them all emails (probably this one, verbatim). The list of email addresses was apparently assembled manually, and his argument seems reasonable, but the tool in question originally comes from the {{l/ip|Kiwi Farms}} online terrorism organization (thankfully now defunct). <html><details><summary><b>email from Jeffrey Freeman</b></summary></html> [[File:2022-11.screen.qoto.1.png|thumb|a QOTO user mentions the tool]] [[File:2022-11.screen.qoto.2.png|thumb|JF plans to email the admins of instances that have defederated from QOTO]] [[File:KF.fedi-block.screen.png|thumb|screenshot of the tool in question, clearly showing its KF provenance]] <blockquote> {{i/sub|email}} </blockquote><html></details></html> 384bb5efb8cd7934f8c75723b47ce39763657f09 0 145 469 2022-11-18T01:19:16Z Woozle 1 Created page with "{{page/date}} * [[/QOTO]]: we blocked them awhile back; they recently reached out about it..." wikitext text/x-wiki {{page/date}} * [[/QOTO]]: we blocked them awhile back; they recently reached out about it... db71ff171cf8a8e88e73bc0d710cfb1775597075 0 1 470 461 2022-11-18T01:19:24Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks * Most recent day-journal entry (probably): [[2022/11/17]] ==Site News== * '''[[2020-03-31]]''' site going down for an upgrade * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 97f5b9854e18a030ae2b05f3d1c2cd15c3c8af9d 489 470 2022-11-18T15:55:10Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Site News== * '''[[2020-03-31]]''' site going down for an upgrade * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> ca60cb73d3395e43630b6dd4821a95f308c7cd7b 6 146 471 2022-11-18T01:22:57Z Woozle 1 [[category:screenshot]] wikitext text/x-wiki == Summary == [[category:screenshot]] dc2a039a71f4df6b0291834b1b96ac10f518e061 6 147 472 2022-11-18T01:26:07Z Woozle 1 [[category:screenshot]] [[category:deleted]] * '''from''' [https://qoto.org/@freemo/109360881187600726 qoto.org] (now deleted) wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:deleted]] * '''from''' [https://qoto.org/@freemo/109360881187600726 qoto.org] (now deleted) a27c6f2c9cbf56a334c3a68a3f2a0ef02ef064e4 6 148 473 2022-11-18T01:29:10Z Woozle 1 [[category:screenshot]] * '''what''': screenshot of a {{l/ip|KiwiFarms}} tool for searching out instances that are blocking a given instance wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': screenshot of a {{l/ip|KiwiFarms}} tool for searching out instances that are blocking a given instance 39195256fad05fbbbe38abeac9b7ddfee842a88d 474 473 2022-11-18T01:29:30Z Woozle 1 Woozle moved page [[File:Kf.fedi-block.screen.png]] to [[File:KF.fedi-block.screen.png]] wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': screenshot of a {{l/ip|KiwiFarms}} tool for searching out instances that are blocking a given instance 39195256fad05fbbbe38abeac9b7ddfee842a88d 476 474 2022-11-18T01:32:51Z Woozle 1 wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': screenshot of a {{l/ip|Kiwi Farms}} tool for searching out instances that are blocking a given instance * '''retrieved''' from [https://fba.ryona.agency/ fba.ryona.agency] ** '''Note''': the Git repo to which it links is no longer available because KF lost their domain. 03167013bfacd9add99dcd6912b1a5ee111beab5 6 149 475 2022-11-18T01:29:30Z Woozle 1 Woozle moved page [[File:Kf.fedi-block.screen.png]] to [[File:KF.fedi-block.screen.png]] wikitext text/x-wiki #REDIRECT [[File:KF.fedi-block.screen.png]] a55b534c9b9b7f97e7a228c00075ed6fd43b96b0 0 150 481 2022-11-18T13:41:32Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https:..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance. While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, which means that anti-science content and toxic users are allowed to proliferate. Numerous users (on and off TootCat) have brought this to our attention. On [[2022/11/17]], Jeffrey Freeman (believed to be the admin or possibly owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. 996825562ac3218dd05a1550afd615d4c6b5d57f 482 481 2022-11-18T13:46:24Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance. While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, which means that anti-science content and toxic users are allowed to proliferate. Numerous users (on and off TootCat) have brought this to our attention. On [[2022/11/17]], Jeffrey Freeman (believed to be the admin or possibly owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. fb4fb96f5ea8ac93c3c5ee5efbc14edc42820f10 490 482 2022-11-18T16:17:13Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance. While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, which means that anti-science content and toxic users are allowed to proliferate. Numerous users (on and off TootCat) have brought this to our attention. The domain was registered on 2008-05-31, long before Mastodon existed, and appears to have initially been used to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. On [[2022/11/17]], Jeffrey Freeman (believed to be the admin or possibly owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> 6c56a1b77b5a8240cb30b6f53a42350ff819e99d 495 490 2022-11-18T17:55:08Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance. While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, which means that anti-science content and toxic users are allowed to proliferate. Numerous users (on and off TootCat) have brought this to our attention. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others". On [[2022/11/17]], Jeffrey Freeman (believed to be the admin or possibly owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> f61b271b594b8c314b4bf605612c06c691a46936 496 495 2022-11-18T17:58:12Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance. While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, which means that anti-science content and toxic users are allowed to proliferate. Numerous users (on and off TootCat) have brought this to our attention. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others" and the site had 19 users. On [[2022/11/17]], Jeffrey Freeman (believed to be the admin or possibly owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> 7c99951024e94b33f3e71c86ead62befd6cbb988 497 496 2022-11-18T18:06:18Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance with a "free speech" approach to moderation. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others" and the site had 19 users. ==Issues== While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, potentially allowing anti-science content and toxic users to proliferate. Numerous users (on and off TootCat) have brought this problem to our attention. At the present time, however, we have no specific examples of problematic posts. Using "#[https://qoto.org/tags/woke woke]" as an example of a politically-charged tag, I found mostly positive/reasonable posts and none which seem problematic. On [[2022/11/17]], Jeffrey Freeman (apparently the domain owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> e708279d72ac7b5ba744844a4f5f64c70e29ff3e 498 497 2022-11-18T18:14:03Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance with a "free speech" approach to moderation. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others" and the site had 19 users. ==Issues== While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, potentially allowing anti-science content and toxic users to proliferate. Numerous users (on and off TootCat) have brought this problem to our attention. At the present time, however, we have no specific examples of problematic posts. Using "#[https://qoto.org/tags/woke woke]" as an example of a politically-charged tag, I found mostly positive/reasonable posts and relatively few which seem problematic. (Notes: [https://qoto.org/@b_chocolatey/109329018486628722]) They do federate with [[noagendasocial.com|NoAgendaSocial]] and with [[brighteon.social]] which hosts anti-science site Natural News, and their main feed consequently does contain a small but significant quantity of right-wing BS. On [[2022/11/17]], Jeffrey Freeman (apparently the domain owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> 559cfaa3d2181d554288fdb005c150169ae217b8 500 498 2022-11-18T22:12:01Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance with a "free speech" approach to moderation. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others" and the site had 19 users. ==Issues== While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, potentially allowing anti-science content and toxic users to proliferate. Numerous users (on and off TootCat) have brought this problem to our attention. At the present time, however, we have no specific examples of problematic posts. Using "#[https://qoto.org/tags/woke woke]" as an example of a politically-charged tag, I found mostly positive/reasonable posts and relatively few which seem problematic. (Notes: [https://qoto.org/@b_chocolatey/109329018486628722]) They do federate with [[noagendasocial.com|NoAgendaSocial]] and with [[brighteon.social]] which hosts anti-science site Natural News, and their main feed consequently does contain a small but significant quantity of right-wing BS. On [[2022/11/17]], Jeffrey Freeman (apparently the domain owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. * '''2018-12-06''' qoto.org has 2149 users<ref name=qoto-archive-8 /> * '''2018-11-07''' qoto.org has 1936 users<ref name=qoto-archive-7 /> * '''2018-10-07''' qoto.org has 1799 users<ref name=qoto-archive-6 /> * '''2018-09-02''' qoto.org has 1433 users<ref name=qoto-archive-5 /> * '''2018-08-15''' qoto.org has 112 users<ref name=qoto-archive-4 /> * '''2018-08-07''' qoto.org has 102 users<ref name=qoto-archive-3 /> * '''2018-07-10''' qoto.org has 19 users<ref name=qoto-archive-2 />; first appearance in archive.org ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-3>'''2018-08-07 archive''': [https://web.archive.org/web/20180807123948/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-4>'''2018-08-15 archive''': [https://web.archive.org/web/20180815233147/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-5>'''2018-09-02 archive''': [https://web.archive.org/web/20180902134516/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-6>'''2018-10-07 archive''': [https://web.archive.org/web/20181007173538/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-7>'''2018-11-07 archive''': [https://web.archive.org/web/20181107154717/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-8>'''2018-12-06 archive''': [https://web.archive.org/web/20181206143118/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> f1487869a4356a26b992a3124996cd255e14bfb7 10 151 483 2022-11-18T15:03:22Z Woozle 1 Created page with "<noinclude>[[category:inclusion]]</noinclude>{{:{{PAGENAME}}/{{{1}}}}}" wikitext text/x-wiki <noinclude>[[category:inclusion]]</noinclude>{{:{{PAGENAME}}/{{{1}}}}} dcffd4974910820e81079c1cf65316c9cf3a1914 0 152 484 2022-11-18T15:05:31Z Woozle 1 Created page with "'''received''': 2022-11-17 15:13 EST ---- Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our pol..." wikitext text/x-wiki '''received''': 2022-11-17 15:13 EST ---- Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: : 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. : 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). : 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <html><details><summary><b>original post</b></summary></html><blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote><html></details></html> </blockquote><html></details></html> db745b57e19c95f072ba8c20e5946edb3d1403fb 485 484 2022-11-18T15:05:57Z Woozle 1 wikitext text/x-wiki '''received''': 2022-11-17 15:13 EST ---- Hi, I noticed you had QOTO blocked, I figured this might be a mistake as there has, for some time, been attempts to lie about our policies by some users we blocked for hate speech and sadly some of the community followed along. Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies. At one point he even attempted to create accounts on QOTO that posted hate speech and despite getting suspended shortly after, by doing so in the middle of the night, some of it was noticed for the short time it was up.  My guess is some of this misinformation made its way to you and you, understandably, may have blocked our instance. We also had some similar trouble many years ago where the LGBTQ community was being attacked and they fled, en masse to our server (which is how our server became so popular early on). This caused several people to attack us in a similar manner spreading quite a few lies as well. For more information detailing that incident please see this post, it also explains our subscribe feature, which is privacy-respecting and provides the same level of access as using an RSS reader to follow an account: https://qoto.org/@freemo/109319817943835261 I urge you to actually review our timeline and see for yourself, hate speech, harassment, misinformation, etc has never been tolerated in our instance and still is not. To recap some of the misinformation: : 1) We have very strict and aggressively enforced policies against hate speech in all forms, you wont find any on our timeline and if you do and report it you will find it is usually acted on with a suspension very quickly. : 2) Our subscribe feature is privacy respecting and was specifically implemented to protect the physical safety of our LGBTQ community during their mass exodus to QOTO in the early years. Similarly, for their protection and at their request, is why we only silence servers and do not suspend them (see the post I linked above for the details on this). : 3) harassment and other issues are also strictly enforced on our server. If you wish to discuss this further please feel free to reach out to me either by email or by reaching out to me at [https://qoto.org/@freemo @freemo@qoto.org] ---- In case you have trouble following the link above to the post I referenced I will include the text of that post below for your convenience. <html><details><summary><b>original post</b></summary></html><blockquote> I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the newcomers on QOTO who don't know the history: So there are some servers out there that demand every server in the network block every instance they do, and if a server doesn't block an instance they block then they block you in retaliation. Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, that's how blocks work. The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers. This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesn't block and be blocked by a small handful of servers. Obviously that means on QOTO you will have a bigger view of the world than you would on any of these other servers. In fact QOTO has one of the largest federation footprints of any server in the network. I want to also explain why we chose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people to read content from any server (but with strict hate speech rules). This caused a huge influx of people,specifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name bigots (like milo yiannopoulos) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously. In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway. Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse, </blockquote><html></details></html> 2e0da5bfe0a4f599c1ab437f520aa7f76d357538 0 153 486 2022-11-18T15:10:47Z Woozle 1 Created page with "{{page/date}} Analysis of [[2022/11/17/QOTO|yesterday's QOTO email]] will be [[/QOTO|here]]." wikitext text/x-wiki {{page/date}} Analysis of [[2022/11/17/QOTO|yesterday's QOTO email]] will be [[/QOTO|here]]. d02279967e4dd1397cb1de80f117c04239046aff 501 486 2022-11-19T00:49:04Z Woozle 1 wikitext text/x-wiki {{page/date}} * Analysis of [[2022/11/17/QOTO|yesterday's QOTO email]] will be [[/QOTO|here]]. * Today's sudden {{l/sub|sluggishness}} is just the additional thing we needed. It's great. 21b2e66d6df4863aafdaf25fd5eced428199192c 10 154 491 2022-11-18T16:18:45Z Woozle 1 Created page with "<span style="background: #ffff00;">{{{1}}}</span>" wikitext text/x-wiki <span style="background: #ffff00;">{{{1}}}</span> 8378dfcd08553be96a59925d1694b41c000affc8 0 155 492 2022-11-18T16:18:55Z Woozle 1 Created page with "==Overall== Freeman suggests that any claims of QOTO supporting hate speech and/or bad science are the work of one or more saboteurs, pointing in particular to one former QOTO..." wikitext text/x-wiki ==Overall== Freeman suggests that any claims of QOTO supporting hate speech and/or bad science are the work of one or more saboteurs, pointing in particular to one former QOTO user ("Snow") whom he specifically believes did intentionally sabotage the site by creating sockpuppet accounts on QOTO after being banned. {{hilite|EDITING STILL IN PROGRESS}} (just saving my work) ==Details== {{fmt/quote|attempts to lie about our policies by some users we blocked for hate speech}} * No receipts provided. * Does not specify what those users said that was untrue, but merely attempts to {{l/ip|ad hominem}} them by implying they posted hate speech. {{fmt/quote|Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies.}} * No receipts (links, screenshots, quotes) provided. {{fmt/quote|...[many years ago] the LGBTQ community was being attacked and they fled, en masse to our server...}} * This seems unlikely to me. Mastodon was first deployed in 2016, and when I first encountered it in 2017 most sites were very LGBTQ-friendly (and often run by LGBTQ people). ed2d00f7f3ec797ee1f2d1be9c5eee7ce1b71dd4 499 492 2022-11-18T22:00:17Z Woozle 1 wikitext text/x-wiki ==Overall== Freeman suggests that any claims of QOTO supporting hate speech and/or bad science are the work of one or more saboteurs, pointing in particular to one former QOTO user ("Snow") whom he specifically believes did intentionally sabotage the site by creating sockpuppet accounts on QOTO after being banned. {{hilite|EDITING STILL IN PROGRESS}} (just saving my work) ==Details== {{fmt/quote|attempts to lie about our policies by some users we blocked for hate speech}} * No receipts provided. * Does not specify what those users said that was untrue, but merely attempts to {{l/ip|ad hominem}} them by implying they posted hate speech. {{fmt/quote|Snow, some years back, was blocked for hate speech and he began a campaign against us spoofing various users claiming we accept hate speech on our instance and other outright lies.}} * No receipts (links, screenshots, quotes) provided. {{fmt/quote|...[many years ago] the LGBTQ community was being attacked and they fled, en masse to our server...}} * This seems unlikely to me. Mastodon was first deployed in 2016, and when I first encountered it in 2017 most sites were very LGBTQ-friendly (and often run by LGBTQ people). QOTO did not come online as a Mastdon instance until mid-2018, and was fairly small for some months after that e31bc8e47152c5af457e13dec2f5a1ffcc1ed3f5 0 156 493 2022-11-18T16:19:11Z Woozle 1 Created page with "{{subpage/date}} <html><details><summary><b>analysis of QOTO email</b></summary></html> <blockquote> {{i/sub|analysis}} </blockquote><html></details></html>" wikitext text/x-wiki {{subpage/date}} <html><details><summary><b>analysis of QOTO email</b></summary></html> <blockquote> {{i/sub|analysis}} </blockquote><html></details></html> 61d6796f3d37be5b0160bc3b54dcdb13ddddd8a0 0 157 494 2022-11-18T17:54:29Z Woozle 1 Created page with "'''retrieved''' 2022-11-18 <pre> Domain Name: qoto.org Registry Domain ID: 10763b6ff2b84122bf331e583f1025ac-LROR Registrar WHOIS Server: http://whois.godaddy.com Registrar URL..." wikitext text/x-wiki '''retrieved''' 2022-11-18 <pre> Domain Name: qoto.org Registry Domain ID: 10763b6ff2b84122bf331e583f1025ac-LROR Registrar WHOIS Server: http://whois.godaddy.com Registrar URL: http://www.whois.godaddy.com Updated Date: 2022-09-05T04:54:14Z Creation Date: 2008-05-31T03:06:10Z Registry Expiry Date: 2024-05-31T03:06:10Z Registrar: GoDaddy.com, LLC </pre> All ownership data is "redacted for privacy". 9683b18965f3a71bb85d2edae71e0ed105d16e95 0 158 502 2022-11-19T00:58:15Z Woozle 1 Created page with "So, yeah, today the queue just kind of got slammed for no apparent reason. Unfortunately, the Nix build we currently use means that we can't just tweak config files according..." wikitext text/x-wiki So, yeah, today the queue just kind of got slammed for no apparent reason. Unfortunately, the Nix build we currently use means that we can't just tweak config files according to instructions; we have to either tweak existing Nix config files, or write new ones. Or something like that. ...though apparently there is a documented methodology for adding on the config-stuff we need; I just haven't had the brain-cycles to read any substantial docs yet, much less understand what's going on. We'll get this beast under control eventually. (See [[2022/11/16]] "upgrade plan" discussion for what our plan was ''before'' the current queuesplosion.) 0fc492eccd995cac4ba3f79ea7cc08c9abc66edd 504 502 2022-11-19T01:12:36Z Woozle 1 wikitext text/x-wiki So, yeah, today the queue just kind of got [https://toot.cat/@woozle/109365481486307156 slammed] for no apparent reason. Unfortunately, the Nix build we currently use means that we can't just tweak config files according to instructions; we have to either tweak existing Nix config files, or write new ones. Or something like that. ...though apparently there is a documented methodology for adding on the config-stuff we need; I just haven't had the brain-cycles to read any substantial docs yet, much less understand what's going on. We'll get this beast under control eventually. (See [[2022/11/16]] "upgrade plan" discussion for what our plan was ''before'' the current queuesplosion.) (The queue is now around 260k -- twice as bad as earlier, and much higher than I've ever seen it before.) 5c1ac2c5e2e70a8773cf603165e47f7a102f0b7b 0 89 503 459 2022-11-19T01:09:49Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-18 20:08 EST''' Things are slower again -- even slowerer than before.|There is some discussion [[2022/11/18/sluggishness|here]].}} d79e1150374e814fd652faa066d8ffe2440fc887 505 503 2022-11-19T14:48:30Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2022-11-19 A.M.''' Viv fixed the queue ^.^|We still need to work on [[2022/11/16|upgrading]], however.}} c4e39ec753ffa7dea88bd2493d64bf3e31789d9c 506 505 2022-11-19T14:48:46Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2022-11-19 A.M.''' Viv fixed the queue ^.^|We still need to work on [[2022/11/16|upgrading]], however.}} e629847d552f570221cfbe3776889c3130ade2c3 0 159 507 2022-11-20T01:07:06Z Woozle 1 Created page with "[[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://mastodon.scot We [https://toot.cat/@news/109343526830497124 plan] to suspend mastodon..." wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://mastodon.scot We [https://toot.cat/@news/109343526830497124 plan] to suspend [[mastodon.scot]] on [[2022/11/26]], for allowing a police union presence. Since then we've also had a [https://toot.cat/@doe/109373299962130775 report] that they were very reluctant to suspend a transphobe, so that seems to validate the decision. e89c7c2772d30fd8841ecb22b5d76cee5efeee4b 512 507 2022-11-20T01:28:26Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://mastodon.scot We [https://toot.cat/@news/109343526830497124 plan] to suspend [[mastodon.scot]] on [[2022/11/26]], for allowing a police union presence. Since then we've also had a report that they were very reluctant to suspend a transphobe, so that seems to validate the decision. 27cd0faa33d7c334d0a54419b0d58cf419c204ec 6 160 508 2022-11-20T01:11:28Z Woozle 1 [[category:screenshot]] * '''what''': screenshot of [[toot.community]]'s logo and site slogan * '''retrieved''' 2022-11-19 wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': screenshot of [[toot.community]]'s logo and site slogan * '''retrieved''' 2022-11-19 3d99beda05672e06139a7246d8bb1d0377c6b21b 0 161 509 2022-11-20T01:13:02Z Woozle 1 Created page with "[[category:instance]] [[category:mastodon]] [[category:limited]] File:2022-11-19 at 20-09-41.screen.toot.community.logo-slogan.png|thumb|Site slogan: {{fmt/quote|We're a gen..." wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] [[File:2022-11-19 at 20-09-41.screen.toot.community.logo-slogan.png|thumb|Site slogan: {{fmt/quote|We're a generic, free-for-all Mastodon instance hosted in The Netherlands. We're welcoming to all that seek a place of enjoyment online while being excellent to each other.}} How can you be excellent to each other while also being a free-for-all?]] * '''site''': https://toot.community We [https://toot.cat/@news/109343526830497124 plan] to suspend [[toot.community]] on [[2022/11/26]] for refusing to suspend transmisic journalist Suzanne Moore. (So much for being excellent to each other.) e2be599fb8485006c624cd416d489a31b19ee3cc 0 162 510 2022-11-20T01:24:43Z Woozle 1 Created page with "[[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://union.place TootCat [https://toot.cat/@news/109343526830497124 plans to suspend] unio..." wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://union.place TootCat [https://toot.cat/@news/109343526830497124 plans to suspend] [[union.place]] on [[2022/11/26]], for allowing presence of {{l/wp|AFL–CIO}}, a union known for racism<ref name=SocWork /> and the support of police unions.<ref name=NewRep /> ==Footnotes== <references> <ref name=NewRep>'''2020-05-29''' [https://newrepublic.com/article/157918/no-cop-unions No More Cop Unions] {{fmt/quote|The International Union of Police Associations, which represents over 100,000 law enforcement employees as well as emergency medical personnel, is officially affiliated with the}} AFL-CIO... {{fmt/quote|But if the federation wants to prove that it’s seriously committed to racial justice and true worker solidarity, the AFL-CIO must permanently disaffiliate from the IUPA and sever its ties with any and all other police associations.}}</ref> <ref name=SocWork>'''1986-01''' [http://socialistworker.org/2012/06/28/blacks-and-the-great-depression Blacks and the Great Depression] talks about the history of racism in the AFL; it's not clear if this is still a problem.</ref> </references> d78a5f5dad763a530fb778f7a16ff7b73d34e6a2 14 163 511 2022-11-20T01:26:01Z Woozle 1 Created page with "{{lc|instance}}s and individuals whose access to TootCat has been limited (blocked, silenced, etc.)" wikitext text/x-wiki {{lc|instance}}s and individuals whose access to TootCat has been limited (blocked, silenced, etc.) eabfd08f51492846be4f1d5df4369d9600ae9166 0 164 513 2022-11-20T01:49:02Z Woozle 1 Created page with "[[category:instance]] [[category:mastodon]] * '''site''': https://journa.host [[journa.host]] [https://journa.host/@info/109372514074976879 suspended] two users, stating that..." wikitext text/x-wiki [[category:instance]] [[category:mastodon]] * '''site''': https://journa.host [[journa.host]] [https://journa.host/@info/109372514074976879 suspended] two users, stating that {{fmt/quote|One published several posts attacking the integrity of another, who is a moderator on the server. The second user published a post demeaning the professionalism of a journalist, based on their identity.}} What they did not note is that the first one had published transmisic content, and the second one had called that into question. This seems like a classic example of journalistic "both sides"ing. Apparently the critic was Parker Molloy, and the criticized admin is one Mike Pesca. Much criticism ensued (saving links in case the original post is deleted, making them hard to find): * https://artisan.chat/@Curator/109372833092319826 * https://eightpoint.app/@naebumaye/109373097757641673 * https://mastodon.lol/@littletranspunk/109372845075445910 * https://kolektiva.social/@estrapade/109372874668095616 * https://mastodon.social/@MrJM/109372896735323733 - apparently the moderator is known bigot Mike Pesca * https://kolektiva.social/@nullillx/109372909921526012 * https://kolektiva.social/@maegrenofwithy/109372918108069150 * https://chaos.social/@Aphrodite/109373049184169062 * https://eightpoint.app/@Slaanesh/109372928654632387 * https://eightpoint.app/@kittenbitten/109373107104840720 * https://mstdn.social/@ostrich/109372933981211984 * https://teh.entar.net/@spacehobo/109372958258454893 * https://jorts.horse/@ancient_catbus/109372951869232369 * https://jorts.horse/@ancient_catbus/109373061197910794 * https://orbsafe.masto.host/@edclayand/109373274397268512 * https://orbsafe.masto.host/@edclayand/109373305266712231 * https://toot.community/@jimmyrayreid/109372980266604486 * https://mastodon.social/@bryceyoungquist/109373030682680647 * https://jorts.horse/@ancient_catbus/109373213182248265 * https://eightpoint.app/@rozietoez/109373006839076570 * https://eightpoint.app/@kittenbitten/109373114563174910 * https://dresden.network/@catherina/109373050489240975 * https://jorts.horse/@peptostate/109373090803125817 * https://eldritch.cafe/@getdizzy/109373106126382630 * https://writing.exchange/@XanIndigo/109373191302823221 * https://cybre.space/@asmallteapot/109373215222120706 * https://mstdn.social/@leahmcelrath/109373401849200070 * https://todon.nl/@joenepraat/109373441448198360 - screenshot showing journa.host's "no transphobia" policy 5508e82b15afe0ed187cdc2d7f3dd56370f875a6 0 165 516 515 2022-11-20T17:56:43Z Woozle 1 2 revisions imported: moved from HTYP wikitext text/x-wiki I'm not sure any of this is actually related to the problem... no mention of the user in question. <pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' Feb 10 18:51:15 tootcat2 sshd[7271]: Connection closed by 118.25.110.158 port 37586 [preauth] Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.308Z 30030 TID-owp9kkfe6 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.311Z 30030 TID-owp9kkfe6 WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.313Z 30030 TID-owp9kkfe6 WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.953Z 30030 TID-gphwttvbm WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.954Z 30030 TID-gphwttvbm WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.955Z 30030 TID-gphwttvbm WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.176Z 30030 TID-gphwjiv5e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.177Z 30030 TID-gphwjiv5e WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.178Z 30030 TID-gphwjiv5e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:23 tootcat2 sshd[7349]: Invalid user hate from 194.44.154.76 port 26361 Feb 10 18:52:24 tootcat2 sshd[7349]: Received disconnect from 194.44.154.76 port 26361:11: Bye Bye [preauth] Feb 10 18:52:24 tootcat2 sshd[7349]: Disconnected from invalid user hate 194.44.154.76 port 26361 [preauth] Feb 10 18:52:31 tootcat2 sshd[7358]: Connection closed by 218.161.34.78 port 58004 [preauth] Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.521Z 30030 TID-owp6t798e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.584Z 30030 TID-owp6t798e WARN: Stoplight::Error::RedLight: Delivery failed for https://osada.usezot.net/inbox: https://osada.usezot.net/inbox Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.736Z 30030 TID-owp6t798e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.122Z 30030 TID-owpcdbkfq WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' </pre> ec7166dc087fbb9de402ee5c27621bcc212a7329 584 516 2022-11-20T17:59:30Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2019/02/10]] to [[2019/02/10]] without leaving a redirect: indended location wikitext text/x-wiki I'm not sure any of this is actually related to the problem... no mention of the user in question. <pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' Feb 10 18:51:15 tootcat2 sshd[7271]: Connection closed by 118.25.110.158 port 37586 [preauth] Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.308Z 30030 TID-owp9kkfe6 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.311Z 30030 TID-owp9kkfe6 WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.313Z 30030 TID-owp9kkfe6 WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.953Z 30030 TID-gphwttvbm WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.954Z 30030 TID-gphwttvbm WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.955Z 30030 TID-gphwttvbm WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.176Z 30030 TID-gphwjiv5e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.177Z 30030 TID-gphwjiv5e WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.178Z 30030 TID-gphwjiv5e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:23 tootcat2 sshd[7349]: Invalid user hate from 194.44.154.76 port 26361 Feb 10 18:52:24 tootcat2 sshd[7349]: Received disconnect from 194.44.154.76 port 26361:11: Bye Bye [preauth] Feb 10 18:52:24 tootcat2 sshd[7349]: Disconnected from invalid user hate 194.44.154.76 port 26361 [preauth] Feb 10 18:52:31 tootcat2 sshd[7358]: Connection closed by 218.161.34.78 port 58004 [preauth] Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.521Z 30030 TID-owp6t798e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.584Z 30030 TID-owp6t798e WARN: Stoplight::Error::RedLight: Delivery failed for https://osada.usezot.net/inbox: https://osada.usezot.net/inbox Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.736Z 30030 TID-owp6t798e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.122Z 30030 TID-owpcdbkfq WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' </pre> ec7166dc087fbb9de402ee5c27621bcc212a7329 595 584 2022-11-20T18:05:54Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/08/25|prev]] .. [[../10|today]] .. [[2020-03-31|next]] }} I'm not sure any of this is actually related to the problem... no mention of the user in question. <pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' Feb 10 18:51:15 tootcat2 sshd[7271]: Connection closed by 118.25.110.158 port 37586 [preauth] Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.308Z 30030 TID-owp9kkfe6 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.311Z 30030 TID-owp9kkfe6 WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.313Z 30030 TID-owp9kkfe6 WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.953Z 30030 TID-gphwttvbm WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.954Z 30030 TID-gphwttvbm WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.955Z 30030 TID-gphwttvbm WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.176Z 30030 TID-gphwjiv5e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.177Z 30030 TID-gphwjiv5e WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.178Z 30030 TID-gphwjiv5e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:23 tootcat2 sshd[7349]: Invalid user hate from 194.44.154.76 port 26361 Feb 10 18:52:24 tootcat2 sshd[7349]: Received disconnect from 194.44.154.76 port 26361:11: Bye Bye [preauth] Feb 10 18:52:24 tootcat2 sshd[7349]: Disconnected from invalid user hate 194.44.154.76 port 26361 [preauth] Feb 10 18:52:31 tootcat2 sshd[7358]: Connection closed by 218.161.34.78 port 58004 [preauth] Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.521Z 30030 TID-owp6t798e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.584Z 30030 TID-owp6t798e WARN: Stoplight::Error::RedLight: Delivery failed for https://osada.usezot.net/inbox: https://osada.usezot.net/inbox Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.736Z 30030 TID-owp6t798e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.122Z 30030 TID-owpcdbkfq WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' </pre> 4040955652309ea7b1ae081e6579adc9fec0832a 599 595 2022-11-20T18:18:49Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/08/25|prev]] .. [[../10|today]] .. [[2020/03/31|next]] }} I'm not sure any of this is actually related to the problem... no mention of the user in question. <pre> Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.736Z 30030 TID-owp8kdi66 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:51:13 tootcat2 bundle[30030]: 2019-02-10T18:51:13.737Z 30030 TID-owp8kdi66 WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' Feb 10 18:51:15 tootcat2 sshd[7271]: Connection closed by 118.25.110.158 port 37586 [preauth] Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.308Z 30030 TID-owp9kkfe6 WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.311Z 30030 TID-owp9kkfe6 WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:51:19 tootcat2 bundle[30030]: 2019-02-10T18:51:19.313Z 30030 TID-owp9kkfe6 WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.953Z 30030 TID-gphwttvbm WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.954Z 30030 TID-gphwttvbm WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.955Z 30030 TID-gphwttvbm WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: OpenSSL::SSL::SSLError: Delivery failed for https://osada.usezot.net/inbox: SSL_connect returned=1 errno=0 state=er Feb 10 18:52:05 tootcat2 bundle[30030]: 2019-02-10T18:52:05.957Z 30030 TID-gphwhe6qy WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/http-3.3.0/lib/http/timeout/per_operation.rb:34:in `connect_nonbl Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.176Z 30030 TID-gphwjiv5e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.177Z 30030 TID-gphwjiv5e WARN: Stoplight::Error::RedLight: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox Feb 10 18:52:12 tootcat2 bundle[30030]: 2019-02-10T18:52:12.178Z 30030 TID-gphwjiv5e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:23 tootcat2 sshd[7349]: Invalid user hate from 194.44.154.76 port 26361 Feb 10 18:52:24 tootcat2 sshd[7349]: Received disconnect from 194.44.154.76 port 26361:11: Bye Bye [preauth] Feb 10 18:52:24 tootcat2 sshd[7349]: Disconnected from invalid user hate 194.44.154.76 port 26361 [preauth] Feb 10 18:52:31 tootcat2 sshd[7358]: Connection closed by 218.161.34.78 port 58004 [preauth] Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.521Z 30030 TID-owp6t798e WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.584Z 30030 TID-owp6t798e WARN: Stoplight::Error::RedLight: Delivery failed for https://osada.usezot.net/inbox: https://osada.usezot.net/inbox Feb 10 18:52:42 tootcat2 bundle[30030]: 2019-02-10T18:52:42.736Z 30030 TID-owp6t798e WARN: /home/mastodon/live/vendor/bundle/ruby/2.6.0/gems/stoplight-2.1.3/lib/stoplight/light/runnable.rb:46:in `run_red' Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.122Z 30030 TID-owpcdbkfq WARN: {"context":"Job raised exception","job":{"class":"ActivityPub::DeliveryWorker","args":["{\"@context\":[\"https://ww Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: Mastodon::UnexpectedResponseError: Delivery failed for https://mastodon.rocks/inbox: https://mastodon.rocks/inbox r Feb 10 18:52:44 tootcat2 bundle[30030]: 2019-02-10T18:52:44.144Z 30030 TID-owpcdbkfq WARN: /home/mastodon/live/app/workers/activitypub/delivery_worker.rb:40:in `block (2 levels) in perform_request' </pre> d16cb102deb5ad229ebadb984704ad8143e11596 0 166 518 517 2022-11-20T17:56:43Z Woozle 1 1 revision imported: moved from HTYP wikitext text/x-wiki ==from Discord== <poem> http://tootcat2.hypertwins.net/.well-known/acme-challenge/nLguP2F142gk3WBcZm4BSF86dEp6zMs8_5nmHXADpuM is returning a 404, and just quickly I can't tell where the actual file is supposed to be. I'll look at it later, hopefully in a couple of hours, if I get a chance, but thought I should give you a heads-up just in case. Saving debug log to /var/log/letsencrypt/letsencrypt.log WoozleToday at 10:01 AM Looking into this now. The problem may be on the file-writing site... though I'm getting conflicting information... Nginx is giving me the same problem Apache gives me: I can't tell what file it's trying to access in response to the URL. WoozleToday at 11:13 AM Okay, so... there's a Nginx directive that's not working as intended, and figuring out directive syntax is one of my major weak spots. This:<pre> location ^~ /.well-known/acme-challenge/ { root /var/www/challenges; }</pre> ...seems like it's supposed to strip out the /.well-known/acme-challenge/ from the URL, and append whatever's left to /var/www/challenges. So http://tootcat2.hypertwins.net/.well-known/acme-challenge/test.txt would result in an access to /var/www/challenges/test.txt. But it's not; it's actually resulting in an access to /var/www/challenges/.well-known/acme-challenge/test.txt. But this is a location I can work with, so I'm not going to try to understand the location directive beyond noting that this is how it is effectively working. The next problem is that the certbot seems to be failing to create the test file... unless it is deleting it after the test fails, but from what I remember it doesn't do that; it leaves the files in place for diagnostic purposes. And the most recent test files are from back in May. I changed the certbot config in Webmin so it points directly to /var/www/challenges/.well-known/acme-challenge/, and that seems to have worked. ...but Firefox still says toot.cat's SSL expires on Aug. 28. Maybe I have to restart nginx again? Or restart Mastodon? Dang, what's that command to check a cert from the CLI... openssl something, I think... Oh good, I made notes: https://htyp.org/openssl openssl s_client -connect toot.cat:443 -- okay, great, gives me lots of info that does not include the expiration date. The secret code phrase is apparently: echo | openssl s_client -connect toot.cat:443 2>/dev/null | openssl x509 -noout -dates ...and this confirms that the expiry is still 3 days from now. WoozleToday at 12:01 PM Got it. I'm not sure if Let's Encrypt will renew properly next time, though; the config was clearly kind of messed up. I tried to tidy it, but I'm guessing about some pieces. </poem> 03916e7fd54bdce5f7bf539e069d35fcc9c7ca8d 585 518 2022-11-20T17:59:49Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/08/25]] to [[2018/08/25]] without leaving a redirect: indended location wikitext text/x-wiki ==from Discord== <poem> http://tootcat2.hypertwins.net/.well-known/acme-challenge/nLguP2F142gk3WBcZm4BSF86dEp6zMs8_5nmHXADpuM is returning a 404, and just quickly I can't tell where the actual file is supposed to be. I'll look at it later, hopefully in a couple of hours, if I get a chance, but thought I should give you a heads-up just in case. Saving debug log to /var/log/letsencrypt/letsencrypt.log WoozleToday at 10:01 AM Looking into this now. The problem may be on the file-writing site... though I'm getting conflicting information... Nginx is giving me the same problem Apache gives me: I can't tell what file it's trying to access in response to the URL. WoozleToday at 11:13 AM Okay, so... there's a Nginx directive that's not working as intended, and figuring out directive syntax is one of my major weak spots. This:<pre> location ^~ /.well-known/acme-challenge/ { root /var/www/challenges; }</pre> ...seems like it's supposed to strip out the /.well-known/acme-challenge/ from the URL, and append whatever's left to /var/www/challenges. So http://tootcat2.hypertwins.net/.well-known/acme-challenge/test.txt would result in an access to /var/www/challenges/test.txt. But it's not; it's actually resulting in an access to /var/www/challenges/.well-known/acme-challenge/test.txt. But this is a location I can work with, so I'm not going to try to understand the location directive beyond noting that this is how it is effectively working. The next problem is that the certbot seems to be failing to create the test file... unless it is deleting it after the test fails, but from what I remember it doesn't do that; it leaves the files in place for diagnostic purposes. And the most recent test files are from back in May. I changed the certbot config in Webmin so it points directly to /var/www/challenges/.well-known/acme-challenge/, and that seems to have worked. ...but Firefox still says toot.cat's SSL expires on Aug. 28. Maybe I have to restart nginx again? Or restart Mastodon? Dang, what's that command to check a cert from the CLI... openssl something, I think... Oh good, I made notes: https://htyp.org/openssl openssl s_client -connect toot.cat:443 -- okay, great, gives me lots of info that does not include the expiration date. The secret code phrase is apparently: echo | openssl s_client -connect toot.cat:443 2>/dev/null | openssl x509 -noout -dates ...and this confirms that the expiry is still 3 days from now. WoozleToday at 12:01 PM Got it. I'm not sure if Let's Encrypt will renew properly next time, though; the config was clearly kind of messed up. I tried to tidy it, but I'm guessing about some pieces. </poem> 03916e7fd54bdce5f7bf539e069d35fcc9c7ca8d 601 585 2022-11-20T18:51:12Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/07/18|prev]] .. [[2018/08/25|today]] .. [[2019/02/10|next]] }} ==from Discord== <poem> http://tootcat2.hypertwins.net/.well-known/acme-challenge/nLguP2F142gk3WBcZm4BSF86dEp6zMs8_5nmHXADpuM is returning a 404, and just quickly I can't tell where the actual file is supposed to be. I'll look at it later, hopefully in a couple of hours, if I get a chance, but thought I should give you a heads-up just in case. Saving debug log to /var/log/letsencrypt/letsencrypt.log WoozleToday at 10:01 AM Looking into this now. The problem may be on the file-writing site... though I'm getting conflicting information... Nginx is giving me the same problem Apache gives me: I can't tell what file it's trying to access in response to the URL. WoozleToday at 11:13 AM Okay, so... there's a Nginx directive that's not working as intended, and figuring out directive syntax is one of my major weak spots. This:<pre> location ^~ /.well-known/acme-challenge/ { root /var/www/challenges; }</pre> ...seems like it's supposed to strip out the /.well-known/acme-challenge/ from the URL, and append whatever's left to /var/www/challenges. So http://tootcat2.hypertwins.net/.well-known/acme-challenge/test.txt would result in an access to /var/www/challenges/test.txt. But it's not; it's actually resulting in an access to /var/www/challenges/.well-known/acme-challenge/test.txt. But this is a location I can work with, so I'm not going to try to understand the location directive beyond noting that this is how it is effectively working. The next problem is that the certbot seems to be failing to create the test file... unless it is deleting it after the test fails, but from what I remember it doesn't do that; it leaves the files in place for diagnostic purposes. And the most recent test files are from back in May. I changed the certbot config in Webmin so it points directly to /var/www/challenges/.well-known/acme-challenge/, and that seems to have worked. ...but Firefox still says toot.cat's SSL expires on Aug. 28. Maybe I have to restart nginx again? Or restart Mastodon? Dang, what's that command to check a cert from the CLI... openssl something, I think... Oh good, I made notes: https://htyp.org/openssl openssl s_client -connect toot.cat:443 -- okay, great, gives me lots of info that does not include the expiration date. The secret code phrase is apparently: echo | openssl s_client -connect toot.cat:443 2>/dev/null | openssl x509 -noout -dates ...and this confirms that the expiry is still 3 days from now. WoozleToday at 12:01 PM Got it. I'm not sure if Let's Encrypt will renew properly next time, though; the config was clearly kind of messed up. I tried to tidy it, but I'm guessing about some pieces. </poem> 2056d0fb3c56ecaf4a10b8287f4261e78cb349d2 0 167 520 519 2022-11-20T17:56:43Z Woozle 1 1 revision imported: moved from HTYP wikitext text/x-wiki This is going to involve some experimentation, as I've never used Amazon services before and don't intend to start until they reform (not expecting this to happen). My current plan is: # Use [[rclone]] ([https://rclone.org/ web]) to determine how much space current media takes up. # Ensure I have a volume or "space" on DigitalOcean sufficient to accommodate that amount. # Use rclone to copy the media over. # Reconfigure toot.cat's Mastodon to point at the new location. # Leave this configuration in place for a few days, looking for issues and making sure everything is being served by the new location. # Tell PolymerWitch she can turn off the Amazon service, at long last. b1836754d4695d5f42ba9b596b7d2fe7c5a66f69 586 520 2022-11-20T18:00:04Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/07/18]] to [[2018/07/18]] without leaving a redirect: indended location wikitext text/x-wiki This is going to involve some experimentation, as I've never used Amazon services before and don't intend to start until they reform (not expecting this to happen). My current plan is: # Use [[rclone]] ([https://rclone.org/ web]) to determine how much space current media takes up. # Ensure I have a volume or "space" on DigitalOcean sufficient to accommodate that amount. # Use rclone to copy the media over. # Reconfigure toot.cat's Mastodon to point at the new location. # Leave this configuration in place for a few days, looking for issues and making sure everything is being served by the new location. # Tell PolymerWitch she can turn off the Amazon service, at long last. b1836754d4695d5f42ba9b596b7d2fe7c5a66f69 602 586 2022-11-20T18:52:46Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/06/22|prev]] .. [[2018/07/18|today]] .. [[2018/08/25|next]] }} This is going to involve some experimentation, as I've never used Amazon services before and don't intend to start until they reform (not expecting this to happen). My current plan is: # Use {{l/htyp|rclone}} ([https://rclone.org/ web]) to determine how much space current media takes up. # Ensure I have a volume or "space" on DigitalOcean sufficient to accommodate that amount. # Use rclone to copy the media over. # Reconfigure toot.cat's Mastodon to point at the new location. # Leave this configuration in place for a few days, looking for issues and making sure everything is being served by the new location. # Tell PolymerWitch she can turn off the Amazon service, at long last. b3b1cf87b065741e7afbab8298ad88861db90c95 0 168 525 524 2022-11-20T17:56:43Z Woozle 1 4 revisions imported: moved from HTYP wikitext text/x-wiki This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooted (which wasn't strictly necessary, but the system was asking for one because of a kernel upgrade some days ago). ...and then it turned out I had forgotten to save my changes before rebooting, so I had to do this: <pre> root@tootcat2:~# systemctl restart mastodon-sidekiq.service Warning: mastodon-sidekiq.service changed on disk. Run 'systemctl daemon-reload' to reload units. root@tootcat2:~# systemctl daemon-reload </pre> After finding [https://discourse.joinmastodon.org/t/lots-of-activerecord-connectiontimeouterror/994/3 this explanation], I understood two things: * <code>DB_POOL</code> should be the same as the <code>sidekiq -c</code> value * I actually have plenty of CPU headroom, and can boost this quite a bit more. I first tried 40, and that helped a bit -- but the "busy" queue was still getting stuck around 3500. So then I bumped it up to 100, and within a minute or two the queue was down under 100. Also, do things in ''this'' order:<pre> root@tootcat2:~# systemctl daemon-reload root@tootcat2:~# systemctl restart mastodon-sidekiq.service </pre> eb5280265607129bd7970e1c05f14b11db1dfb5e 587 525 2022-11-20T18:00:20Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/06/22]] to [[2018/06/22]] without leaving a redirect: indended location wikitext text/x-wiki This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooted (which wasn't strictly necessary, but the system was asking for one because of a kernel upgrade some days ago). ...and then it turned out I had forgotten to save my changes before rebooting, so I had to do this: <pre> root@tootcat2:~# systemctl restart mastodon-sidekiq.service Warning: mastodon-sidekiq.service changed on disk. Run 'systemctl daemon-reload' to reload units. root@tootcat2:~# systemctl daemon-reload </pre> After finding [https://discourse.joinmastodon.org/t/lots-of-activerecord-connectiontimeouterror/994/3 this explanation], I understood two things: * <code>DB_POOL</code> should be the same as the <code>sidekiq -c</code> value * I actually have plenty of CPU headroom, and can boost this quite a bit more. I first tried 40, and that helped a bit -- but the "busy" queue was still getting stuck around 3500. So then I bumped it up to 100, and within a minute or two the queue was down under 100. Also, do things in ''this'' order:<pre> root@tootcat2:~# systemctl daemon-reload root@tootcat2:~# systemctl restart mastodon-sidekiq.service </pre> eb5280265607129bd7970e1c05f14b11db1dfb5e 603 587 2022-11-20T18:54:01Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/05/30|prev]] .. [[2018/06/22|today]] .. [[2018/07/18|next]] }} This isn't the first time this has happened... outgoing toots are being delayed by something like 1.5-2 hours. Last time, we upped the number of threads from 15 to 25 (according to my memory; apparently we didn't document it), and that seemed to fix the blockage. So this time, I'm making notes. Editing <code>/etc/systemd/system/mastodon-sidekiq.service</code>: * changing <code>DB_POOL=5</code> to <code>DB_POOL=20</code> * changing <code>sidekiq -c 25</code> to <code>sidekiq -c 40</code> ...and rebooted (which wasn't strictly necessary, but the system was asking for one because of a kernel upgrade some days ago). ...and then it turned out I had forgotten to save my changes before rebooting, so I had to do this: <pre> root@tootcat2:~# systemctl restart mastodon-sidekiq.service Warning: mastodon-sidekiq.service changed on disk. Run 'systemctl daemon-reload' to reload units. root@tootcat2:~# systemctl daemon-reload </pre> After finding [https://discourse.joinmastodon.org/t/lots-of-activerecord-connectiontimeouterror/994/3 this explanation], I understood two things: * <code>DB_POOL</code> should be the same as the <code>sidekiq -c</code> value * I actually have plenty of CPU headroom, and can boost this quite a bit more. I first tried 40, and that helped a bit -- but the "busy" queue was still getting stuck around 3500. So then I bumped it up to 100, and within a minute or two the queue was down under 100. Also, do things in ''this'' order:<pre> root@tootcat2:~# systemctl daemon-reload root@tootcat2:~# systemctl restart mastodon-sidekiq.service </pre> d235915d9c642671d78db173eaf431d5211edeba 0 169 533 532 2022-11-20T17:56:43Z Woozle 1 7 revisions imported: moved from HTYP wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * <s>I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS).</s> ** '''2018-06-28''' This was causing full-page 403 errors for some users; I reverted the Nginx config file and it [https://toot.cat/@news/100281876187861211 seems to be fixed now]. *** commented out the port 80 no-redirect block *** uncommented the old port 80 redirect block *** added an IPv6 listen directive to the uncommented block *** <code>/etc/init.d/nginx reload</code> * <s>A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.)</s> ===Relevant Files=== * <code>/etc/cron.daily/letsencrypt-renew</code> - the [[cron]] job to check/renew the cert * <code>/etc/letsencrypt/renewal/tootcat.conf</code> - Let's Encrypt configuration * <code>/etc/nginx/sites-available/tootcat.conf</code> - Nginx configuration * <code>/var/log/nginx/access.log</code> - Nginx access log (showed 404 when accessing via IPv6) ==Narration / Notes== ===Phase 1=== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ===Phase 2=== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ===Phase 3=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 4=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 5=== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 4c15baafb8c616cb8730338852c9165f35c4dfcc 588 533 2022-11-20T18:00:34Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/05/30]] to [[2018/05/30]] without leaving a redirect: indended location wikitext text/x-wiki ==Solved== There were, I think, two main problems: * The [[Let's Encrypt]] configuration had not been properly set up after the [[User:Woozle/toot.cat/2018/04/10|server migration in April]] * [[Nginx]] was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the [[letsencrypt]] command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using [[wget]] to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * <s>I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS).</s> ** '''2018-06-28''' This was causing full-page 403 errors for some users; I reverted the Nginx config file and it [https://toot.cat/@news/100281876187861211 seems to be fixed now]. *** commented out the port 80 no-redirect block *** uncommented the old port 80 redirect block *** added an IPv6 listen directive to the uncommented block *** <code>/etc/init.d/nginx reload</code> * <s>A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.)</s> ===Relevant Files=== * <code>/etc/cron.daily/letsencrypt-renew</code> - the [[cron]] job to check/renew the cert * <code>/etc/letsencrypt/renewal/tootcat.conf</code> - Let's Encrypt configuration * <code>/etc/nginx/sites-available/tootcat.conf</code> - Nginx configuration * <code>/var/log/nginx/access.log</code> - Nginx access log (showed 404 when accessing via IPv6) ==Narration / Notes== ===Phase 1=== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ===Phase 2=== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ===Phase 3=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 4=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 5=== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 4c15baafb8c616cb8730338852c9165f35c4dfcc 604 588 2022-11-20T18:58:52Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/05/20|prev]] .. [[2018/05/30|today]] .. [[2018/06/22|next]] }} ==Solved== There were, I think, two main problems: * The {{l/htyp|Let's Encrypt}} configuration had not been properly set up after the [[2018/04/10|server migration in April]] * {{l/htyp|Nginx}} was correctly configured to respond to IPv6 on port 443 (https), but ''not'' on port 80 (http). ** This was the problem that took the most time to identify, as it caused the {{l/htyp|letsencrypt}} command to fail even though the URL appeared to be returning the proper file. Confounding factors included: * [[HSTS]] was turned on (this seems to be part of the SSL cert, ''not'' something in Nginx), so existing browser sessions insisted on self-redirecting from http to https even when I had turned that off in Nginx. '''Workaround''': only attempt access in an anonymous browser window. (Using {{l/htyp|wget}} to do the test also might have worked &ndash; and ultimately, it was use of wget from an IPv6-enabled server that provided the final clue.) * My home internet (and apparently everyone else's) uses only IPv4, while Let's Encrypt uses IPv6 if it is available &ndash; so Let's Encrypt was consistently reporting a problem that we weren't seeing, leading us to think (basically) that we were misunderstanding the messages. Cleanup to do: * It's not clear whether Let's Encrypt is now set up properly; I did the challenge installation by hand. * <s>I turned off ''all'' http -> https redirects in Nginx in order to be absolutely certain that Nginx wasn't causing the redirects I was still seeing (because of HSTS).</s> ** '''2018-06-28''' This was causing full-page 403 errors for some users; I reverted the Nginx config file and it [https://toot.cat/@news/100281876187861211 seems to be fixed now]. *** commented out the port 80 no-redirect block *** uncommented the old port 80 redirect block *** added an IPv6 listen directive to the uncommented block *** <code>/etc/init.d/nginx reload</code> * <s>A user [https://gist.github.com/renatolond/5102b210849beaef0a443d5d93f4636a now reports] some IPv6 issues on the https side as well. ([https://rm.vbz.net/issues/124 Addressing this] first.)</s> ===Relevant Files=== * <code>/etc/cron.daily/letsencrypt-renew</code> - the [[cron]] job to check/renew the cert * <code>/etc/letsencrypt/renewal/tootcat.conf</code> - Let's Encrypt configuration * <code>/etc/nginx/sites-available/tootcat.conf</code> - Nginx configuration * <code>/var/log/nginx/access.log</code> - Nginx access log (showed 404 when accessing via IPv6) ==Narration / Notes== ===Phase 1=== It looks like nginx was set to use a different set of certificate files than the ones [[Let's Encrypt]] was set to renew. Tentatively, LE goes through all the .conf files in /etc/letsencrypt/renewal and renews each one. There was only one, and it pointed at files in /etc/letsencrypt/live/tootcat2.hypertwins.net/ I've changed it to point to /etc/letsencrypt/live/toot.cat/ Nginx also looks for 2 cert files in /etc/letsencrypt/live/toot.cat/, so now at least we're matched. When I try to renew with letsencrypt renew, I get: <pre> root@tootcat2:/# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:11:15,708:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:11:15,709:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:11:15,711:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/# </pre> The key piece of information there seems to be "Missing --webroot-path for domain". What seems to be happening is that Nginx is redirecting from http to https even though the file exists. ===Phase 2=== It turned out there was an [[HSTS]] policy that was forcing the browser to redirect even though Nginx wasn't, I think? But opening a toot.cat URL in an anonymous window fixed that. However it still wasn't finding the test file, so I changed the webroot on both Nginx and Let'sEncrypt to /var/www/challenges, and then was able to access the test file. ...but Let's Encrypt still returns this: <pre> root@tootcat2:/var/www/challenges# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Encountered exception during recovery 2018-05-31 00:49:39,460:ERROR:letsencrypt.error_handler:Missing --webroot-path for domain: toot.cat Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/error_handler.py", line 74, in call_registered self.funcs[-1]() File "/usr/lib/python2.7/dist-packages/letsencrypt/auth_handler.py", line 280, in _cleanup_challenges self.dv_auth.cleanup(dv_c) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 139, in cleanup root_path = self._get_root_path(achall) File "/usr/lib/python2.7/dist-packages/letsencrypt/plugins/webroot.py", line 108, in _get_root_path .format(achall.domain)) PluginError: Missing --webroot-path for domain: toot.cat 2018-05-31 00:49:39,462:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing --webroot-path for domain: toot.cat. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges# </pre> ===Phase 3=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:30:48,656:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --staging renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:36:59,134:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 4=== <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:42:09,149:WARNING:letsencrypt.client:Registering without email! 2018-05-31 01:42:09,992:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-staging.api.letsencrypt.org/directory (You can set this with the --agree-tos flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:52:59,407:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Failed authorization procedure. toot.c$ t (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://toot.cat/.well-known/acme-challenge/tZFwZb9H2at2brdJYexpRqTDYOigSbT$ J_6oL3AXwBQ: ''[404 errors]''. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) </pre> [...] <pre> root@tootcat2:/var/www/challenges/.well-known# letsencrypt --dry-run --agree-tos --manual renew Processing /etc/letsencrypt/renewal/toot.cat.conf 2018-05-31 01:59:54,703:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/toot.cat.conf produced an unexpected error: Missing command line flag or config entry for this setting: NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you're running letsencrypt in manual mode on a machine that is not your server, please ensure you're okay with that. Are you OK with your IP being logged? (You can set this with the --manual-public-ip-logging-ok flag). Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/toot.cat/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s) root@tootcat2:/var/www/challenges/.well-known# </pre> ===Phase 5=== Relevant excerpts from Discord: <blockquote> <poem> Ok, yeah, same error. It's getting a 404. But the URL it claims to be accessing is returning the challenge. (Just verified again, pasting URL from the logfile.) It'd be nice if it would include the whole URL, including the domain and protocol. Wait, it did. I'm just tired. It's as if the LE remote client is reaching a different server.(edited) Is there any logging of IP address... Can't see any. Okay, next idea; check Nginx server log and see what URL is being requested. If any. ''[...]'' I'm trying to do a close tracking of what request the server sees when I do the test run, but my ADD gets worse when I'm tired and I forget what I was doing between one screen and the next. Ok, I've caught the server actually returning a 404! Checking URL... URL is fine, except I'm making an assumption about the domain. I think that must be the problem. Somehow. There is another domain on that server, and it goes to a different webroot. oh, ffu.... this MIGHT be an IPv6 issue. >.< ''[...]'' I can test this from another DO server. They all have IPv6 and tend to default to it. ''[...]'' It's IPv6. ''[...]'' I just got a 404 from the same URL that works from here. Ok, this should be tractable now. I just have to find an example of correct ipv6 Nginx config. ''[...]'' I can probably just copy from the https section. Found. Now restart nginx... Or reload, I guess. 200 OK So... do I dare try LE the easy way? No, I'd better do it manually again. Actually, better do a manual dry-run first. TEST SUCCESSFUL ''[...]'' Now the real thing (but manually again, because I have zero faith that the other part of the problem is solved). heh... URL ends in UwU... ''[...]'' I got a success message from LE, but still getting cert error in browser. owait, probly need to restart nginx. <hopes that's all it is> Yeah, the standard cron script does that too. Ok... OMGSUCCESS. </poem> </blockquote> 87ecd1d7ca8a45a95ed10770915ece3de3d292a9 0 170 535 534 2022-11-20T17:56:44Z Woozle 1 1 revision imported: moved from HTYP wikitext text/x-wiki * '''symptom''': Main page came up, but with no toots. Some other pages would not respond at all. * '''cause''': ** [[Nginx]] wasn't starting, and the status returned by <code>systemctl status nginx.service</code> included the message <code>bind() to [::]:443 failed (98: Address already in use)</code>. ** This was in turn because of a small problem in <code>/etc/nginx/sites-available/tootcat2.hypertwins.net.conf</code>. The lines of interest are:<pre> server { listen 443 ssl; listen [::]:443 ssl ipv6only=on; </pre> The last line ''was'' set to <code>ipv6only=off</code>. What that apparently means is that this line will try to listen on [[IPv4]] as well &ndash; but the previous line already has nginx trying to listen on IPv4, so nginx fails when it tries to listen again on the same port. Specifying <code>ipv6only=on</code> tells it "this line means you're supposed to ''only'' listen on [[IPv6]], so don't try anything else here.", resulting in nginx listening on both IPv4 and IPv6, which is what we want. I don't know why it was even working before; maybe the behavior of nginx changed between versions. 6369e6c70ba349fee315f74daa07966e793e091c 589 535 2022-11-20T18:00:47Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/05/20]] to [[2018/05/20]] without leaving a redirect: indended location wikitext text/x-wiki * '''symptom''': Main page came up, but with no toots. Some other pages would not respond at all. * '''cause''': ** [[Nginx]] wasn't starting, and the status returned by <code>systemctl status nginx.service</code> included the message <code>bind() to [::]:443 failed (98: Address already in use)</code>. ** This was in turn because of a small problem in <code>/etc/nginx/sites-available/tootcat2.hypertwins.net.conf</code>. The lines of interest are:<pre> server { listen 443 ssl; listen [::]:443 ssl ipv6only=on; </pre> The last line ''was'' set to <code>ipv6only=off</code>. What that apparently means is that this line will try to listen on [[IPv4]] as well &ndash; but the previous line already has nginx trying to listen on IPv4, so nginx fails when it tries to listen again on the same port. Specifying <code>ipv6only=on</code> tells it "this line means you're supposed to ''only'' listen on [[IPv6]], so don't try anything else here.", resulting in nginx listening on both IPv4 and IPv6, which is what we want. I don't know why it was even working before; maybe the behavior of nginx changed between versions. 6369e6c70ba349fee315f74daa07966e793e091c 606 589 2022-11-20T19:03:29Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/05/03|prev]] .. [[2018/05/20|today]] .. [[2018/05/30|next]] }} * '''symptom''': Main page came up, but with no toots. Some other pages would not respond at all. * '''cause''': ** {{l/htyp|Nginx}} wasn't starting, and the status returned by <code>systemctl status nginx.service</code> included the message <code>bind() to [::]:443 failed (98: Address already in use)</code>. ** This was in turn because of a small problem in <code>/etc/nginx/sites-available/tootcat2.hypertwins.net.conf</code>. The lines of interest are:<pre> server { listen 443 ssl; listen [::]:443 ssl ipv6only=on; </pre> The last line ''was'' set to <code>ipv6only=off</code>. What that apparently means is that this line will try to listen on [[IPv4]] as well &ndash; but the previous line already has nginx trying to listen on IPv4, so nginx fails when it tries to listen again on the same port. Specifying <code>ipv6only=on</code> tells it "this line means you're supposed to ''only'' listen on [[IPv6]], so don't try anything else here.", resulting in nginx listening on both IPv4 and IPv6, which is what we want. I don't know why it was even working before; maybe the behavior of nginx changed between versions. e80928a2db79d8229ee230661cb2ffa36f8bc71e 0 171 538 537 2022-11-20T17:56:44Z Woozle 1 2 revisions imported: moved from HTYP wikitext text/x-wiki Reference links: * [https://rm.vbz.net/projects/toot-cat/issues issue on Redmine] * [https://github.com/tootsuite/mastodon/issues/7323 help request on tootsuite@GitHub] ==Solution== # You have to restart (or reload?) the SideKiq job, possibly in addition to the web job. # Installing Postfix and using these settings works well: <pre> SMTP_SERVER=localhost SMTP_PORT=25 SMTP_AUTH_METHOD=none SMTP_OPENSSL_VERIFY_MODE=none </pre> ==Notes== <code>journalctl -u mastodon-sidekiq | grep smtp</code> yields this: <pre> May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' May 03 11:15:21 tootcat2 bundle[5368]: 2018-05-03T11:15:21.238Z 5368 TID-orv43zy6g WARN: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' </pre> ...with several prior instances of very similar sequences. 9bf9145fef6896b83be5faa2106b7c132f007334 590 538 2022-11-20T18:01:09Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/05/03]] to [[2018/05/03]] without leaving a redirect: indended location wikitext text/x-wiki Reference links: * [https://rm.vbz.net/projects/toot-cat/issues issue on Redmine] * [https://github.com/tootsuite/mastodon/issues/7323 help request on tootsuite@GitHub] ==Solution== # You have to restart (or reload?) the SideKiq job, possibly in addition to the web job. # Installing Postfix and using these settings works well: <pre> SMTP_SERVER=localhost SMTP_PORT=25 SMTP_AUTH_METHOD=none SMTP_OPENSSL_VERIFY_MODE=none </pre> ==Notes== <code>journalctl -u mastodon-sidekiq | grep smtp</code> yields this: <pre> May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' May 03 11:15:21 tootcat2 bundle[5368]: 2018-05-03T11:15:21.238Z 5368 TID-orv43zy6g WARN: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' </pre> ...with several prior instances of very similar sequences. 9bf9145fef6896b83be5faa2106b7c132f007334 607 590 2022-11-20T19:04:43Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/04/10|prev]] .. [[2018/05/03|today]] .. [[2018/05/20|next]] }} Reference links: * [https://rm.vbz.net/projects/toot-cat/issues issue on Redmine] * [https://github.com/tootsuite/mastodon/issues/7323 help request on tootsuite@GitHub] ==Solution== # You have to restart (or reload?) the SideKiq job, possibly in addition to the web job. # Installing Postfix and using these settings works well: <pre> SMTP_SERVER=localhost SMTP_PORT=25 SMTP_AUTH_METHOD=none SMTP_OPENSSL_VERIFY_MODE=none </pre> ==Notes== <code>journalctl -u mastodon-sidekiq | grep smtp</code> yields this: <pre> May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' May 03 11:15:21 tootcat2 bundle[5368]: 2018-05-03T11:15:21.238Z 5368 TID-orv43zy6g WARN: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `initialize' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `open' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:539:in `tcp_socket' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:549:in `block in do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:548:in `do_start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/2.5.0/net/smtp.rb:518:in `start' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session' May 03 11:15:21 tootcat2 bundle[5368]: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/mail-2.7.0/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!' </pre> ...with several prior instances of very similar sequences. 3f91c3b4abfa563469c8bb7b8bf34c935585ceb6 0 172 542 541 2022-11-20T17:56:44Z Woozle 1 3 revisions imported: moved from HTYP wikitext text/x-wiki Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] from the start this time, but using Ruby 2.5.0 instead of 2.4.1. Skipping the server-creation and DNS bits because I do those without thinking. (Also, can't point the real domain here until later.) These instructions assume you're running as root, which works for me. * <code>mkdir setup</code> (/root/setup) * <code>cd setup</code> - because I like to keep setup clutter in a separate folder * <code>wget https://deb.nodesource.com/setup_6.x</code> * <code>bash setup_6.x</code> * <code>apt -y install curl</code> - was already the latest version * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> At this point (morning of 4/11), I turned the problem over to Lottie... * [https://gist.github.com/foxsan48/dad39f49777794d60594905e85e8fc45 Gist] * [https://toot.cat/@woozle/99841228289384064 toot to StaticSafe] * There are also some notes in [https://rm.vbz.net/projects/toot-cat-sysops/wiki toot.cat private on Redmine] that could be made public 41097f6906afd91958f13e29e2014b862b160851 591 542 2022-11-20T18:01:23Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/04/10]] to [[2018/04/10]] without leaving a redirect: indended location wikitext text/x-wiki Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] from the start this time, but using Ruby 2.5.0 instead of 2.4.1. Skipping the server-creation and DNS bits because I do those without thinking. (Also, can't point the real domain here until later.) These instructions assume you're running as root, which works for me. * <code>mkdir setup</code> (/root/setup) * <code>cd setup</code> - because I like to keep setup clutter in a separate folder * <code>wget https://deb.nodesource.com/setup_6.x</code> * <code>bash setup_6.x</code> * <code>apt -y install curl</code> - was already the latest version * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> At this point (morning of 4/11), I turned the problem over to Lottie... * [https://gist.github.com/foxsan48/dad39f49777794d60594905e85e8fc45 Gist] * [https://toot.cat/@woozle/99841228289384064 toot to StaticSafe] * There are also some notes in [https://rm.vbz.net/projects/toot-cat-sysops/wiki toot.cat private on Redmine] that could be made public 41097f6906afd91958f13e29e2014b862b160851 608 591 2022-11-20T19:05:54Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/04/07|prev]] .. [[2018/04/10|today]] .. [[2018/05/03|next]] }} Server created: 4GB- 2CPU - 80GB - $20/mo, Ubuntu 16.04, SFO2, IPv6, Gonzo key. Using the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] from the start this time, but using Ruby 2.5.0 instead of 2.4.1. Skipping the server-creation and DNS bits because I do those without thinking. (Also, can't point the real domain here until later.) These instructions assume you're running as root, which works for me. * <code>mkdir setup</code> (/root/setup) * <code>cd setup</code> - because I like to keep setup clutter in a separate folder * <code>wget https://deb.nodesource.com/setup_6.x</code> * <code>bash setup_6.x</code> * <code>apt -y install curl</code> - was already the latest version * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> At this point (morning of 4/11), I turned the problem over to Lottie... * [https://gist.github.com/foxsan48/dad39f49777794d60594905e85e8fc45 Gist] * [https://toot.cat/@woozle/99841228289384064 toot to StaticSafe] * There are also some notes in [https://rm.vbz.net/projects/toot-cat-sysops/wiki toot.cat private on Redmine] that could be made public 68d000dc17db31bf662b3f67d3568a895c19172a 0 173 551 550 2022-11-20T17:56:44Z Woozle 1 8 revisions imported: moved from HTYP wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. ===part 2=== Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. <code>bundle --help</code> gives man-style help which lists all the bundle commands; <code>bundle install --help</code> lists options specific to <code>bundle install</code>, and none of the <code>--with-idn-*</code> options appear to be among either of them. * How about: <code>gem install idn-ruby</code>... nope, same error message... * How about <code>gem install idn-ruby --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code>... ** nope: <code>invalid option: --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ===part 3=== Some [https://cybre.space/@benhamill/99831608699607241 research] by Ben Hamill suggested this: <code>gem install --remote idn</code> The resulting error message pointed me at a log file, which seemed to be saying that the problem was coming from [[gcc]]. Since this means there was compiling involved, I thought maybe I should install the header file for idn as well (as root): <code>apt install libghc-gnuidn-dev</code>. Followed by... * <code>su - mastodon</code> * <code>gem install --remote idn</code> Output: <pre>Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-23716-rrnxuy.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Oops, maybe I was supposed to be in <code>~/live</code>? Logging in again as root... * <code>su - mastodon</code> * <code>cd live</code> * <code>gem install --remote idn</code> Output:<pre> Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-24783-1trgchl.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Looks pretty much the same. All I can think is that this is some kind of version conflict caused by me originally installing the wrong version of Ruby (because that's the version the instructions specified), so let's scrap this build and start over. 55e2d440b7847e48a8eeefbfa9bdb464852b51e2 592 551 2022-11-20T18:01:40Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/04/07]] to [[2018/04/07]] without leaving a redirect: indended location wikitext text/x-wiki =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. ===part 2=== Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. <code>bundle --help</code> gives man-style help which lists all the bundle commands; <code>bundle install --help</code> lists options specific to <code>bundle install</code>, and none of the <code>--with-idn-*</code> options appear to be among either of them. * How about: <code>gem install idn-ruby</code>... nope, same error message... * How about <code>gem install idn-ruby --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code>... ** nope: <code>invalid option: --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ===part 3=== Some [https://cybre.space/@benhamill/99831608699607241 research] by Ben Hamill suggested this: <code>gem install --remote idn</code> The resulting error message pointed me at a log file, which seemed to be saying that the problem was coming from [[gcc]]. Since this means there was compiling involved, I thought maybe I should install the header file for idn as well (as root): <code>apt install libghc-gnuidn-dev</code>. Followed by... * <code>su - mastodon</code> * <code>gem install --remote idn</code> Output: <pre>Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-23716-rrnxuy.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Oops, maybe I was supposed to be in <code>~/live</code>? Logging in again as root... * <code>su - mastodon</code> * <code>cd live</code> * <code>gem install --remote idn</code> Output:<pre> Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-24783-1trgchl.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Looks pretty much the same. All I can think is that this is some kind of version conflict caused by me originally installing the wrong version of Ruby (because that's the version the instructions specified), so let's scrap this build and start over. 55e2d440b7847e48a8eeefbfa9bdb464852b51e2 609 592 2022-11-20T19:07:18Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/01/15|prev]] .. [[2018/04/07|today]] .. [[2018/04/10|next]] }} =Take 1= Loosely following [https://anystack.xyz/how-to-install-mastodon-ubuntu/ these instructions]... I just do everything in root rather than using sudo, because that's how I roll. Things done: * Create droplet (4GB- 2CPU - 80GB - $20, Ubuntu 16.04, SFO2, IPv6, Gonzo key) * <code>apt update</code> * <code>apt upgrade</code> * install node.js: ** <code>curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -</code> ** <code>apt install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev nodejs</code> ** <code>npm install -g yarn</code> * install redis-server: ** <code>apt install redis-server redis-tools</code> * install [[PostgreSQL]] (Pg): ** <code>apt install postgresql postgresql-contrib</code> * switch to postgres user, create Mastodon user in Pg: ** <code>su - postgres</code> ** <code>psql</code> ** <code>CREATE USER mastodon CREATEDB;</code> ** <code>\q</code> Now, we're trying to enable ident auth in Pg so users can log in without a password. * I don't understand why we want to do this; seems like bad security. * I tried to do this bit exactly as written, because it looked like it might be user-sensitive, but it didn't work (see below). * Can this be done as all one line? * <code>sudo sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' \</code> * <code>/etc/postgresql/9.?/main/pg_hba.conf</code> That didn't work, because after the second line it asked for a password for postgres, which I don't have, and wouldn't accept a blank. So, backing out and trying as root (and all one line): * <code>sed -i '/^local.*postgres.*peer$/a host all all 127.0.0.1/32 ident' /etc/postgresql/9.?/main/pg_hba.conf</code> No error, but also no success message. I will assume successful. * install ident daemon: ** <code>apt install pidentd</code> ** <code>systemctl enable pidentd</code> ** Response: *** <code>pidentd.service is not a native service, redirecting to systemd-sysv-install</code> *** <code>Executing /lib/systemd/systemd-sysv-install enable pidentd</code> ** <code>systemctl start pidentd</code> ** <code>systemctl restart postgresql</code> ==Setting Up Ruby== * <code>apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev rbenv</code> ** Note: the instructions omitted <code>rbenv</code>, but it seems to be needed. * <code>adduser --disabled-password --disabled-login mastodon</code> ** Just hitting ENTER in response to all questions, "Y" in response to "Y/n". * Change to user <code>mastodon</code> (which also puts you in <code>/home/mastodon</code>): ** <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * install Ruby 2.4.1: ** <code>rbenv install 2.4.1</code> That didn't work because rbenv was not installed. (Also not sure this is the best version of Ruby, anymore, but that seems fixable later now that we have the command). So I had to back out to root, <code>apt install rbenv</code>, and then <code>su - mastodon</code> again. * <code>rbenv install 2.4.1</code> ** This takes a couple of minutes. * <code>rbenv global 2.4.1</code> ** This is instantaneous. * <code>ruby -v</code> ** response: <code>ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]</code> *** ...um, okay. ==Installing Mastodon== * <code>cd ~</code> ** This is probably redundant. * <code>git clone https://github.com/tootsuite/mastodon.git live</code> * <code>cd live</code> * <code>git checkout $(git tag | tail -n 1)</code> ** I don't know what this does. * "Install bundler to manage the dependencies and disable the gem documentation." ** <code>echo "gem: --no-document" > ~/.gemrc</code> ** <code>gem install bundler --no-ri</code> *** Response: **** <code>Fetching: bundler-1.16.1.gem (100%)</code> **** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> **** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> Okay, '''Simon says'''... * <code>exit</code> * <code>gem install bundler --no-ri</code> ** Response: *** <code>Fetching: bundler-1.16.1.gem (100%)</code> *** <code>Successfully installed bundler-1.16.1</code> *** <code>1 gem installed</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** A bunch of stuff happened, and then this error message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2653-idvqpi.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out An error occurred while installing nokogiri (1.8.2), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.8.2'` succeeds before bundling. In Gemfile: rails-settings-cached was resolved to 0.6.6, which depends on rails was resolved to 5.1.4, which depends on actioncable was resolved to 5.1.4, which depends on actionpack was resolved to 5.1.4, which depends on actionview was resolved to 5.1.4, which depends on rails-dom-testing was resolved to 2.0.3, which depends on nokogiri </pre> Okay, trying that command... * <code>gem install nokogiri -v '1.8.2'</code> ** Response: *** <code>Fetching: mini_portile2-2.3.0.gem (100%)</code> *** <code>ERROR: While executing gem ... (Gem::FilePermissionError)</code> *** <code> You don't have write permissions for the /var/lib/gems/2.3.0 directory.</code> So again, Simon says... * <code>exit</code> * <code>gem install nokogiri -v '1.8.2'</code> ** Response: <pre>Fetching: mini_portile2-2.3.0.gem (100%) Successfully installed mini_portile2-2.3.0 Fetching: nokogiri-1.8.2.gem (100%) Building native extensions. This could take a while... ERROR: Error installing nokogiri: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/nokogiri-1.8.2/ext/nokogiri /usr/bin/ruby2.3 -r ./siteconf20180407-2736-1uhzyd6.rb extconf.rb mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h extconf failed, exit code 1 Gem files will remain installed in /var/lib/gems/2.3.0/gems/nokogiri-1.8.2 for inspection. Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nokogiri-1.8.2/gem_make.out </pre> Okay. Let's start over, and use the [https://github.com/staticsafe/mastodon-documentation/blob/master/Running-Mastodon/Production-Guide.md official instructions] this time, leaving off any bits that have already clearly been done. (I don't know why I didn't use them to begin with... I guess these alternate instructions just looked so distro-specific and friendly.) =Take 2= As root... * <code>cd /root</code> * <code>mkdir setup</code> * <code>cd setup</code> * <code>wget https://deb.nodesource.com/setup_6.x</code> * ...and then "review the script" using <code>less</code> -- as if I'd know how to evaluate it. Glanced at it, what does it mean. Now running it... * </code>bash setup_6.x</code> ==Yarn Repository== * <code>apt -y install curl</code> ** was already installed, but might not have been if I hadn't tried the other instructions first * <code>curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -</code> * <code>echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list</code> * <code>apt update</code> * Install [[Yarn]] plus a bunch of other stuff: ** <code>apt -y install imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib nginx letsencrypt yarn</code> ==User-Specific Stuff== * <code>su - mastodon</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> ** This does not seem to have been done earlier, or at least not with the same command -- but there is a .rbenv folder. So can't do it again, unless we want to erase it. Maybe later, if something seems to be wrong with rbenv. * <code>cd ~/.rbenv && src/configure && make -C src</code> ** Response: <code>-su: src/configure: No such file or directory</code> ** Okay, something seems to be wrong with rbenv. * <code>cd ~</code> * <code>rm -rdf .rbenv</code> * <code>git clone https://github.com/rbenv/rbenv.git ~/.rbenv</code> * <code>cd ~/.rbenv && src/configure && make -C src</code> * <code>echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc</code> * <code>echo 'eval "$(rbenv init -)"' >> ~/.bashrc</code> * Restart the shell: ** <code>exec bash</code> * Check if rbenv is correctly installed: ** <code>type rbenv</code> *** Response:<pre> rbenv is a function rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</pre> * Install ruby-build as rbenv plugin: ** <code>git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build</code> * <code>rbenv install 2.4.1</code> ** This is probably redundant now, but why not. ** It still takes a couple of minutes, though. * <code>rbenv global 2.4.1</code> ==Installing Mastodon== Much of this has already been done -- but this instruction set does explain it a bit. Skipping redundant bits... * Install bundler (again, but without the options): ** <code>gem install bundler</code> * Use bundler to install the rest of the Ruby dependencies (this might be redundant, but maybe not): ** <code>bundle install --deployment --without development test</code> *** Response: <code>Could not locate Gemfile</code> I have to stop for tonight. ===part 2=== Looks like [[Gemfile]] is an app-config file which needs to already exist when you run <code>bundle install [...]</code> -- and there's one in <code>/home/mastodon/live</code>, so let's run it from there. Log in as root, then: * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response: <code>rbenv: version `2.5.0' is not installed (set by /home/mastodon/live/.ruby-version)</code> Looks like the instructions may not have been updated; Charlotte tells me that Masto does, in fact, now require Ruby 2.5.0. So... * <code>cd ~</code> * <code>rbenv install 2.5.0</code> * <code>rbenv global 2.5.0</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre>rbenv: bundle: command not found The `bundle' command exists in these Ruby versions: 2.4.1 </pre> I'm going on the assumption that this doesn't mean "Ruby did away with Bundler after 2.4.1" but rather "You haven't installed it for 2.5.0, you've only installed it for 2.4.1". We're already in ~/live, which seems to be the right folder, so no need to cd there. * <code>gem install bundler</code> *: <code>Successfully installed bundler-1.16.1</code> *: <code>1 gem installed</code> * <code>bundle install --deployment --without development test</code> ** This seemed to be running successfully for quite awhile, installing various things, then failed with the following message: <pre> Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-7030-grmz7k.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Get back out to root, then: * <code>apt install idn</code> * <code>su - mastodon</code> * <code>cd live</code> * <code>bundle install --deployment --without development test</code> ** Response:<pre> Installing idn-ruby 0.1.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-19186-1hcp4ek.rb extconf.rb checking for -lidn... no ERROR: could not find idn library! Please install the GNU IDN library or alternatively specify at least one of the following options if the library can only be found in a non-standard location: --with-idn-dir=/path/to/non/standard/location or --with-idn-lib=/path/to/non/standard/location/lib --with-idn-include=/path/to/non/standard/location/include *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/home/mastodon/.rbenv/versions/2.5.0/bin/$(RUBY_BASE_NAME) --with-idn-dir --without-idn-dir --with-idn-include --without-idn-include=${idn-dir}/include --with-idn-lib --without-idn-lib=${idn-dir}/lib --with-idnlib --without-idnlib To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/mastodon/live/vendor/bundle/ruby/2.5.0/gems/idn-ruby-0.1.0 for inspection. Results logged to /home/mastodon/live/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-ruby-0.1.0/gem_make.out An error occurred while installing idn-ruby (0.1.0), and Bundler cannot continue. Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling. In Gemfile: idn-ruby </pre> Ohhkayy... well... let's try pointing it directly at the idn library file... * <code>bundle install --deployment --without development test --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ** Response: <code>Unknown switches '--with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11'</code> *** Okay, so the error message is lying to me, or I'm misreading it. <code>bundle --help</code> gives man-style help which lists all the bundle commands; <code>bundle install --help</code> lists options specific to <code>bundle install</code>, and none of the <code>--with-idn-*</code> options appear to be among either of them. * How about: <code>gem install idn-ruby</code>... nope, same error message... * How about <code>gem install idn-ruby --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code>... ** nope: <code>invalid option: --with-idn-lib=/usr/lib/x86_64-linux-gnu/libidn.so.11</code> ===part 3=== Some [https://cybre.space/@benhamill/99831608699607241 research] by Ben Hamill suggested this: <code>gem install --remote idn</code> The resulting error message pointed me at a log file, which seemed to be saying that the problem was coming from [[gcc]]. Since this means there was compiling involved, I thought maybe I should install the header file for idn as well (as root): <code>apt install libghc-gnuidn-dev</code>. Followed by... * <code>su - mastodon</code> * <code>gem install --remote idn</code> Output: <pre>Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-23716-rrnxuy.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Oops, maybe I was supposed to be in <code>~/live</code>? Logging in again as root... * <code>su - mastodon</code> * <code>cd live</code> * <code>gem install --remote idn</code> Output:<pre> Building native extensions. This could take a while... ERROR: Error installing idn: ERROR: Failed to build gem native extension. current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext /home/mastodon/.rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180409-24783-1trgchl.rb extconf.rb checking for -lidn... yes checking for idna.h... yes checking for punycode.h... yes checking for stringprep.h... yes creating Makefile current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" clean current directory: /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2/ext make "DESTDIR=" compiling idn.c compiling idna.c idna.c: In function ‘toASCII’: idna.c:88:37: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_ascii_8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: In function ‘toUnicode’: idna.c:128:41: error: ‘struct RString’ has no member named ‘ptr’ rc = idna_to_unicode_8z8z(RSTRING(str)->ptr, &buf, flags); ^ idna.c: At top level: cc1: warning: unrecognized command line option ‘-Wno-self-assign’ cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’ cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’ cc1: warning: unrecognized command line option ‘-Wno-tautological-compare’ Makefile:241: recipe for target 'idna.o' failed make: *** [idna.o] Error 1 make failed, exit code 2 Gem files will remain installed in /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/idn-0.0.2 for inspection. Results logged to /home/mastodon/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0-static/idn-0.0.2/gem_make.out </pre> Looks pretty much the same. All I can think is that this is some kind of version conflict caused by me originally installing the wrong version of Ruby (because that's the version the instructions specified), so let's scrap this build and start over. 2ce97feac9c4b11aa16e83dc2e840ec2ac7e170f 0 174 555 554 2022-11-20T17:56:44Z Woozle 1 3 revisions imported: moved from HTYP wikitext text/x-wiki My original request on Jan. 11: <blockquote> How do I move toot.cat out of the "BS10413-GANDI" sub-account (which I did not create, and which has "limited permissions" that I don't see how to edit) and into my main account ("woozle", the one I am writing from) so that I can manage DNS and automatic renewals? Thank you. </blockquote> In the meantime, I ''did'' figure out how to adjust the DNS, so this only becomes a crisis when I need to renew the domain. Four days later, here's the response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the launch of V5). Domains are fully imported only if the owner account has been migrated too. Domains for which the migrated account is only Administrative, Technical and/or Billing contact are partially imported under an Organization with limited permissions (or need to be synchronized to be displayed). Domain "toot.cat" has another "classic" account as owner (and need synchronization) that's why it was not displayed. No it appears under an organization named "BS10413-GANDI" which is in fact the Owner 'classic' handle. To get full rights on the domain you will have to ask the owner to migrate his account to V5, or you will have to migrate the owner account and merge it with your current V5 account. For this case go to the "Classic" interface to verify you have access to this account (password mostly) and verify that the email address and legal informations (Name or company name, account type) match exactly the ones for your account and or organization. If this is not the case you will have to make "change owner account" operation to a new 'classic' handle with the correct informations. http://wiki.gandi.net/en/contacts/changeowner A change of owner mean the validation of an email sent to the email address registered for each of the owner. I invite you to verify specifically that the email addresses fo the owners are correct, valid and that no Anti Spam or Whois privacy service is activated. This operation is just an administrative one, and there would be no impact on the running of the domains or their services. Only domains can be "moved" from one account to another. Other products like SSL certificates, websites or hosting are "locked" to the account which create them. Then go to V5 and log out of the V5 account. Then log in using the classic handle (complete BS10413-GANDI) and password, to trigger the migration process. You can find more information on our new V5 interface at this address: https://doc.gandi.net/en# Do not hesitate to contact us if you need more information. Our best wishes for a happy and successful New Year. Best regards <pre> \o/ Thierry G http://v4.gandi.net/ ------------------------------------------------------------------------------- Are you satisfied with the quality of the reply you received? YES: https://v4.gandi.net/faq/feedback/yes NO: https://v4.gandi.net/faq/feedback/no no I would like to give more detailed feedback: https://v4.gandi.net/faq/feedback. ------------------------------------------------------------------------------- </pre> </blockquote> OMFG what?? I'm thinking it may just be best to get the domain back out of that hellhole, after taking some time to research a better home for it (now that the need is no longer urgent). Possibilities include: * [http://hover.com Hover] (where PolymerWitch originally registered it) * [http://portfast.co.uk portfast.co.uk] ([https://witches.town/@lambdagrrl/99353801843467099 recommendation]) b212fa6f199515e59d6a518734cd5fd3e543184e 593 555 2022-11-20T18:01:55Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/01/15]] to [[2018/01/15]] without leaving a redirect: indended location wikitext text/x-wiki My original request on Jan. 11: <blockquote> How do I move toot.cat out of the "BS10413-GANDI" sub-account (which I did not create, and which has "limited permissions" that I don't see how to edit) and into my main account ("woozle", the one I am writing from) so that I can manage DNS and automatic renewals? Thank you. </blockquote> In the meantime, I ''did'' figure out how to adjust the DNS, so this only becomes a crisis when I need to renew the domain. Four days later, here's the response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the launch of V5). Domains are fully imported only if the owner account has been migrated too. Domains for which the migrated account is only Administrative, Technical and/or Billing contact are partially imported under an Organization with limited permissions (or need to be synchronized to be displayed). Domain "toot.cat" has another "classic" account as owner (and need synchronization) that's why it was not displayed. No it appears under an organization named "BS10413-GANDI" which is in fact the Owner 'classic' handle. To get full rights on the domain you will have to ask the owner to migrate his account to V5, or you will have to migrate the owner account and merge it with your current V5 account. For this case go to the "Classic" interface to verify you have access to this account (password mostly) and verify that the email address and legal informations (Name or company name, account type) match exactly the ones for your account and or organization. If this is not the case you will have to make "change owner account" operation to a new 'classic' handle with the correct informations. http://wiki.gandi.net/en/contacts/changeowner A change of owner mean the validation of an email sent to the email address registered for each of the owner. I invite you to verify specifically that the email addresses fo the owners are correct, valid and that no Anti Spam or Whois privacy service is activated. This operation is just an administrative one, and there would be no impact on the running of the domains or their services. Only domains can be "moved" from one account to another. Other products like SSL certificates, websites or hosting are "locked" to the account which create them. Then go to V5 and log out of the V5 account. Then log in using the classic handle (complete BS10413-GANDI) and password, to trigger the migration process. You can find more information on our new V5 interface at this address: https://doc.gandi.net/en# Do not hesitate to contact us if you need more information. Our best wishes for a happy and successful New Year. Best regards <pre> \o/ Thierry G http://v4.gandi.net/ ------------------------------------------------------------------------------- Are you satisfied with the quality of the reply you received? YES: https://v4.gandi.net/faq/feedback/yes NO: https://v4.gandi.net/faq/feedback/no no I would like to give more detailed feedback: https://v4.gandi.net/faq/feedback. ------------------------------------------------------------------------------- </pre> </blockquote> OMFG what?? I'm thinking it may just be best to get the domain back out of that hellhole, after taking some time to research a better home for it (now that the need is no longer urgent). Possibilities include: * [http://hover.com Hover] (where PolymerWitch originally registered it) * [http://portfast.co.uk portfast.co.uk] ([https://witches.town/@lambdagrrl/99353801843467099 recommendation]) b212fa6f199515e59d6a518734cd5fd3e543184e 610 593 2022-11-20T19:08:59Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2018/01/14|prev]] .. [[2018/01/15|today]] .. [[2018/04/07|next]] }} [[category:gandi]] My original request on Jan. 11: <blockquote> How do I move toot.cat out of the "BS10413-GANDI" sub-account (which I did not create, and which has "limited permissions" that I don't see how to edit) and into my main account ("woozle", the one I am writing from) so that I can manage DNS and automatic renewals? Thank you. </blockquote> In the meantime, I ''did'' figure out how to adjust the DNS, so this only becomes a crisis when I need to renew the domain. Four days later, here's the response from Gandi: <blockquote> Hello, thank you for contacting Gandi Customer Care. We apologize for the delayed answer due to a recent increase of requests (due to the launch of V5). Domains are fully imported only if the owner account has been migrated too. Domains for which the migrated account is only Administrative, Technical and/or Billing contact are partially imported under an Organization with limited permissions (or need to be synchronized to be displayed). Domain "toot.cat" has another "classic" account as owner (and need synchronization) that's why it was not displayed. No it appears under an organization named "BS10413-GANDI" which is in fact the Owner 'classic' handle. To get full rights on the domain you will have to ask the owner to migrate his account to V5, or you will have to migrate the owner account and merge it with your current V5 account. For this case go to the "Classic" interface to verify you have access to this account (password mostly) and verify that the email address and legal informations (Name or company name, account type) match exactly the ones for your account and or organization. If this is not the case you will have to make "change owner account" operation to a new 'classic' handle with the correct informations. http://wiki.gandi.net/en/contacts/changeowner A change of owner mean the validation of an email sent to the email address registered for each of the owner. I invite you to verify specifically that the email addresses fo the owners are correct, valid and that no Anti Spam or Whois privacy service is activated. This operation is just an administrative one, and there would be no impact on the running of the domains or their services. Only domains can be "moved" from one account to another. Other products like SSL certificates, websites or hosting are "locked" to the account which create them. Then go to V5 and log out of the V5 account. Then log in using the classic handle (complete BS10413-GANDI) and password, to trigger the migration process. You can find more information on our new V5 interface at this address: https://doc.gandi.net/en# Do not hesitate to contact us if you need more information. Our best wishes for a happy and successful New Year. Best regards <pre> \o/ Thierry G http://v4.gandi.net/ ------------------------------------------------------------------------------- Are you satisfied with the quality of the reply you received? YES: https://v4.gandi.net/faq/feedback/yes NO: https://v4.gandi.net/faq/feedback/no no I would like to give more detailed feedback: https://v4.gandi.net/faq/feedback. ------------------------------------------------------------------------------- </pre> </blockquote> OMFG what?? I'm thinking it may just be best to get the domain back out of that hellhole, after taking some time to research a better home for it (now that the need is no longer urgent). Possibilities include: * [http://hover.com Hover] (where PolymerWitch originally registered it) * [http://portfast.co.uk portfast.co.uk] ([https://witches.town/@lambdagrrl/99353801843467099 recommendation]) 2a670cd368f717acca86cf47092a81549661bd78 0 175 567 566 2022-11-20T17:56:48Z Woozle 1 11 revisions imported: moved from HTYP wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # configure nginx # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. * [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md Instructions] wanted to configure nginx after installing Mastodon, and this did need to be looked into at some point, so added it as step 5. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} Skipping the bit about installing Ruby, since that is already installed on this server. chdir to <code>/home/tootcat/web</code>, then: : {{markup/tty|tootcat@tootcat:~/web$| git clone https://github.com/tootsuite/mastodon.git mastodon}} :: {{markup/tty|Cloning into 'mastodon'...}} :: {{markup/tty|remote: Counting objects: 56389, done.}} :: {{markup/tty|remote: Compressing objects: 100% (13/13), done.}} :: {{markup/tty|remote: Total 56389 (delta 0), reused 3 (delta 0), pack-reused 56376}} :: {{markup/tty|Receiving objects: 100% (56389/56389), 52.51 MiB | 30.41 MiB/s, done.}} :: {{markup/tty|Resolving deltas: 100% (37140/37140), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon/}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)}} :: {{markup/tty|Note: checking out 'v2.1.3'.}} :: <pre>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 35b8498... Skip ActivityPub Announces of non-public objects (#6230)</pre> : {{markup/tty|tootcat@tootcat:~/web/mastodon$| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|ERROR: While executing gem ... (Gem::FilePermissionError)}} :: {{markup/tty| You don't have write permissions for the /var/lib/gems/2.3.0 directory.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle exec rails c}} :: {{markup/tty/color|red|Could not find rake-12.3.0 in any of the sources}} :: {{markup/tty/color|orange|Run `bundle install` to install missing gems.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install}} :: {{markup/tty/color|orange|Warning: the running version of Bundler (1.15.3) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.}} :: {{markup/tty|Fetching gem metadata from https://rubygems.org/...........}} :: {{markup/tty|Fetching version metadata from https://rubygems.org/...}} :: {{markup/tty|Fetching dependency metadata from https://rubygems.org/..}} :: {{markup/tty|Fetching rake 12.3.0}} <pre> Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run: bundle install --path vendor/bundle to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo. Password: </pre> Decided this was not the way to do it, and logged in as root: : {{markup/tty|root@tootcat:~#| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|Successfully installed bundler-1.16.1}} :: {{markup/tty|Parsing documentation for bundler-1.16.1}} :: {{markup/tty|Installing ri documentation for bundler-1.16.1}} :: {{markup/tty|Done installing documentation for bundler after 9 seconds}} :: {{markup/tty|1 gem installed}} : {{markup/tty|root@tootcat:~#| bundle install --deployment --without development test}} :: {{markup/tty/color|orange|Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.}} :: {{markup/tty/color|red|Could not locate Gemfile}} Okay, so I guess it's back to the mastodon user... : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install --deployment --without development test}} :: This seemed to work: [[/paste/2018/01/14/01]] : {{markup/tty|tootcat@tootcat:~/web/mastodon$ yarn install --pure-lockfile}} :: This also seemed successful, but it also asked me to upgrade Yarn with these specific commands: : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm upgrade --global yarn}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm rebuild node-sass}} <pre> > node-sass@4.7.2 install /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/install.js node-sass build Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node > node-sass@4.7.2 postinstall /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/build.js Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node Testing binary Binary is fine node-sass@4.7.2 /home/tootcat/web/mastodon/node_modules/node-sass </pre> ...and then we move on to configuring Postgres (already done) and nginx, which I think I should add as step 5. ===step 5: configure nginx - ABANDONED for now=== I made a copy of /etc/nginx/sites-available/default and called it toot-cat-new, then changed just a couple of things: * The '''server_name''' was changed from <code>toot.cat</code> to <code>new.toot.cat</code> in two places. ...and then I realized that this plan was going to require setting up extra instances of Puma and the media server (name?) on different ports from 3000 and 4000... which I think I know how to do, but this kinda crosses a threshold into territory uncertain enough that I decided to let a professional do it this time, and live to fight another day. 32a528d6ee58c3f61835830e1668de3dbab8c736 594 567 2022-11-20T18:02:08Z Woozle 1 Woozle moved page [[Woozle/toot.cat/2018/01/14]] to [[2018/01/14]] without leaving a redirect: indended location wikitext text/x-wiki ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # configure nginx # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. * [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md Instructions] wanted to configure nginx after installing Mastodon, and this did need to be looked into at some point, so added it as step 5. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} Skipping the bit about installing Ruby, since that is already installed on this server. chdir to <code>/home/tootcat/web</code>, then: : {{markup/tty|tootcat@tootcat:~/web$| git clone https://github.com/tootsuite/mastodon.git mastodon}} :: {{markup/tty|Cloning into 'mastodon'...}} :: {{markup/tty|remote: Counting objects: 56389, done.}} :: {{markup/tty|remote: Compressing objects: 100% (13/13), done.}} :: {{markup/tty|remote: Total 56389 (delta 0), reused 3 (delta 0), pack-reused 56376}} :: {{markup/tty|Receiving objects: 100% (56389/56389), 52.51 MiB | 30.41 MiB/s, done.}} :: {{markup/tty|Resolving deltas: 100% (37140/37140), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon/}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)}} :: {{markup/tty|Note: checking out 'v2.1.3'.}} :: <pre>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 35b8498... Skip ActivityPub Announces of non-public objects (#6230)</pre> : {{markup/tty|tootcat@tootcat:~/web/mastodon$| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|ERROR: While executing gem ... (Gem::FilePermissionError)}} :: {{markup/tty| You don't have write permissions for the /var/lib/gems/2.3.0 directory.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle exec rails c}} :: {{markup/tty/color|red|Could not find rake-12.3.0 in any of the sources}} :: {{markup/tty/color|orange|Run `bundle install` to install missing gems.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install}} :: {{markup/tty/color|orange|Warning: the running version of Bundler (1.15.3) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.}} :: {{markup/tty|Fetching gem metadata from https://rubygems.org/...........}} :: {{markup/tty|Fetching version metadata from https://rubygems.org/...}} :: {{markup/tty|Fetching dependency metadata from https://rubygems.org/..}} :: {{markup/tty|Fetching rake 12.3.0}} <pre> Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run: bundle install --path vendor/bundle to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo. Password: </pre> Decided this was not the way to do it, and logged in as root: : {{markup/tty|root@tootcat:~#| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|Successfully installed bundler-1.16.1}} :: {{markup/tty|Parsing documentation for bundler-1.16.1}} :: {{markup/tty|Installing ri documentation for bundler-1.16.1}} :: {{markup/tty|Done installing documentation for bundler after 9 seconds}} :: {{markup/tty|1 gem installed}} : {{markup/tty|root@tootcat:~#| bundle install --deployment --without development test}} :: {{markup/tty/color|orange|Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.}} :: {{markup/tty/color|red|Could not locate Gemfile}} Okay, so I guess it's back to the mastodon user... : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install --deployment --without development test}} :: This seemed to work: [[/paste/2018/01/14/01]] : {{markup/tty|tootcat@tootcat:~/web/mastodon$ yarn install --pure-lockfile}} :: This also seemed successful, but it also asked me to upgrade Yarn with these specific commands: : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm upgrade --global yarn}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm rebuild node-sass}} <pre> > node-sass@4.7.2 install /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/install.js node-sass build Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node > node-sass@4.7.2 postinstall /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/build.js Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node Testing binary Binary is fine node-sass@4.7.2 /home/tootcat/web/mastodon/node_modules/node-sass </pre> ...and then we move on to configuring Postgres (already done) and nginx, which I think I should add as step 5. ===step 5: configure nginx - ABANDONED for now=== I made a copy of /etc/nginx/sites-available/default and called it toot-cat-new, then changed just a couple of things: * The '''server_name''' was changed from <code>toot.cat</code> to <code>new.toot.cat</code> in two places. ...and then I realized that this plan was going to require setting up extra instances of Puma and the media server (name?) on different ports from 3000 and 4000... which I think I know how to do, but this kinda crosses a threshold into territory uncertain enough that I decided to let a professional do it this time, and live to fight another day. 32a528d6ee58c3f61835830e1668de3dbab8c736 611 594 2022-11-20T19:10:10Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[no prev] .. [[2018/01/14|today]] .. [[2018/01/15|next]] }} ==2018-01-14== My current plan is: # create new system user "tootcat" # create a new Postgres db for toot.cat's Mastodon # migrate the data there # install Mastodon under user "tootcat" # configure nginx # run Mastodon's schema upgrade rake task # test the result as https://new.toot.cat (get it working) # write a script to automate the data migration # in close succession: ## run the migration script ## reconfigure nginx to point to the new instance ====revisions==== * Decided it would simplify things if I went ahead and created the "tootcat" system user first. * [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md Instructions] wanted to configure nginx after installing Mastodon, and this did need to be looked into at some point, so added it as step 5. ===Notes=== Upgrading Mastodon: ===Work Log=== ====step 1==== Created user and group "tootcat" with /bin/bash as shell, no login allowed. I checked user "polymerwitch" (user for ''current'' Mastodon instance), and it has "sudo" membership -- but I'm not adding that, because it shouldn't be needed. ====step 2==== I'm calling the new db <code>tootcat-masto-r1</code> (toot.cat Mastodon db revision 1). : <code>root@tootcat:~# '''createdb --owner=tootcat tootcat-masto-r1'''</code> :: <code>createdb: could not connect to database template1: FATAL: role "root" does not exist</code> ::: Apparently pg assumes whatever the current system user is as its internal user as well. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: <code>createdb: database creation failed: ERROR: role "tootcat" does not exist</code> : <code>root@tootcat:~# '''createuser --createdb tootcat'''</code> :: <code>createuser: could not connect to database postgres: FATAL: role "root" does not exist</code> - can't say I'm surprised : <code>root@tootcat:~# '''su - postgres -c 'createuser --createdb tootcat''''</code> :: Success. : <code>root@tootcat:~# '''su - postgres -c 'createdb --owner=tootcat tootcat-masto-r1''''</code> :: Success. ====step 3: migrate the data==== Done earlier -- inside <code>/root/backups</code>: : <code>su - postgres -c 'pg_dump mastodon' > tootcat.sql</code> [https://www.postgresql.org/docs/current/static/backup-dump.html Importing the data dump] into the new db: : <code>root@tootcat:~# '''cd /root/scratch'''</code> : <code>root@tootcat:~/scratch# '''ls'''</code> :: <code>tootcat.sql</code> : <code>root@tootcat:~/scratch# '''psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>psql: FATAL: role "root" does not exist</code> ::: I actually expected this, but just wanted to make sure. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql'''</code> :: <code>-su: tootcat.sql: No such file or directory</code> ::: Apparently this operates relative to the <code>postgres</code> user's home folder, or wherever you get put by default when logging in. Okay. : <code>root@tootcat:~/scratch# '''su - postgres -c 'psql tootcat-masto-r1 < /root/scratch/tootcat.sql''''</code> :: <code>-su: /root/scratch/tootcat.sql: Permission denied</code> ::: This is also unsurprising. Other users shouldn't have access to /root files. It was more or less at this point that I discovered that the <code>tootcat.sql</code> file was zero bytes long, so apparently the export process wasn't happy either. There's no <code>/home/postgres</code>, so we can't go there. <code>/root/scratch</code> is already mode 777, so apparently that's insufficient. Oh, but the ''actual'' <code>tootcat.sql</code> file is in <code>/root/backups</code>. Just to be sure, then: : <code>root@tootcat:~/scratch# '''cd ../backups/'''</code> : <code>root@tootcat:~/backups# '''su - postgres -c 'psql tootcat-masto-r1 < /root/backups/tootcat.sql''''</code> :: <code>-su: /root/backups/tootcat.sql: Permission denied</code> ::: As expected. And then it finally occurred to me: : <code>root@tootcat:~/backups# '''su - postgres -c 'pwd''''</code> :: <code>/var/lib/postgresql</code> ::: Oh! Sneaksy, having a home folder outside of the <code>/home</code> folder. Just because <code>/root</code> does it doesn't make it okay; do as I say, not as I do.... : <code>root@tootcat:~/backups# '''cd /var/lib/postgresql/'''</code> : <code>root@tootcat:/var/lib/postgresql# '''mv /root/backups/tootcat.sql ./'''</code> : <code>root@tootcat:/var/lib/postgresql# '''chown postgres:postgres tootcat.sql'''</code> : <code>root@tootcat:/var/lib/postgresql# '''su - postgres -c 'psql tootcat-masto-r1 < tootcat.sql''''</code> :: ...and then stuff started happening that ''might'' have been the output of a successful import. After taking a brief break, I come back to find that the process has completed... and a brief inspection shows that the db seems to be populated with data. I'm calling this step complete, then. ====step 4: installing Mastodon==== The [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Updating-Mastodon-Guide.md official upgrade instructions] mention that you should only ever use "tagged releases on production Mastodon instances", and therefore: <syntaxhighlight lang=bash> su - mastodon cd ~/live git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) </syntaxhighlight> ...except corrected for how things are set up here... and also I need to <code>git clone</code> instead of <code>git pull</code> since I'm doing the upgrade on a fresh deployment rather than in place on an existing one. : {{markup/tty|root@tootcat:/var/lib/postgresql#| cd /home/tootcat}} : {{markup/tty|root@tootcat:/home/tootcat#| su - tootcat}} : {{markup/tty|tootcat@tootcat:~$| mkdir web}} : {{markup/tty|tootcat@tootcat:~$| cd web}} : {{markup/tty|tootcat@tootcat:~/web$| mkdir mastodon}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git clone https://github.com/rbenv/rbenv.git ~/.rbenv}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv'...}} :: {{markup/tty|remote: Counting objects: 2706, done.}} :: {{markup/tty|remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706}} :: {{markup/tty|Receiving objects: 100% (2706/2706), 503.75 KiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (1695/1695), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| cd ~/.rbenv && src/configure && make -C src}} :: {{markup/tty|make: Entering directory '/home/tootcat/.rbenv/src'}} :: {{markup/tty|gcc -fPIC -c -o realpath.o realpath.c}} :: {{markup/tty|gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib -o ../libexec/rbenv-realpath.dylib realpath.o }} :: {{markup/tty|make: Leaving directory '/home/tootcat/.rbenv/src'}} : {{markup/tty|tootcat@tootcat:~/.rbenv$| echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ echo 'eval "$(rbenv init -)"' >> ~/.bashrc}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ exec bash}} : {{markup/tty|tootcat@tootcat:~/.rbenv$ type rbenv}} :: {{markup/tty|rbenv is a function}} <syntaxhighlight lang=ruby>rbenv () { local command; command="${1:-}"; if [ "$#" -gt 0 ]; then shift; fi; case "$command" in rehash | shell) eval "$(rbenv "sh-$command" "$@")" ;; *) command rbenv "$command" "$@" ;; esac }</syntaxhighlight> : {{markup/tty|tootcat@tootcat:~/.rbenv$| git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build}} :: {{markup/tty|Cloning into '/home/tootcat/.rbenv/plugins/ruby-build'...}} :: {{markup/tty|remote: Counting objects: 8588, done.}} :: {{markup/tty|remote: Compressing objects: 100% (25/25), done.}} :: {{markup/tty|remote: Total 8588 (delta 9), reused 24 (delta 3), pack-reused 8556}} :: {{markup/tty|Receiving objects: 100% (8588/8588), 1.79 MiB | 0 bytes/s, done.}} :: {{markup/tty|Resolving deltas: 100% (5481/5481), done.}} :: {{markup/tty|Checking connectivity... done.}} Skipping the bit about installing Ruby, since that is already installed on this server. chdir to <code>/home/tootcat/web</code>, then: : {{markup/tty|tootcat@tootcat:~/web$| git clone https://github.com/tootsuite/mastodon.git mastodon}} :: {{markup/tty|Cloning into 'mastodon'...}} :: {{markup/tty|remote: Counting objects: 56389, done.}} :: {{markup/tty|remote: Compressing objects: 100% (13/13), done.}} :: {{markup/tty|remote: Total 56389 (delta 0), reused 3 (delta 0), pack-reused 56376}} :: {{markup/tty|Receiving objects: 100% (56389/56389), 52.51 MiB | 30.41 MiB/s, done.}} :: {{markup/tty|Resolving deltas: 100% (37140/37140), done.}} :: {{markup/tty|Checking connectivity... done.}} : {{markup/tty|tootcat@tootcat:~/web$| cd mastodon/}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)}} :: {{markup/tty|Note: checking out 'v2.1.3'.}} :: <pre>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 35b8498... Skip ActivityPub Announces of non-public objects (#6230)</pre> : {{markup/tty|tootcat@tootcat:~/web/mastodon$| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|ERROR: While executing gem ... (Gem::FilePermissionError)}} :: {{markup/tty| You don't have write permissions for the /var/lib/gems/2.3.0 directory.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle exec rails c}} :: {{markup/tty/color|red|Could not find rake-12.3.0 in any of the sources}} :: {{markup/tty/color|orange|Run `bundle install` to install missing gems.}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install}} :: {{markup/tty/color|orange|Warning: the running version of Bundler (1.15.3) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.}} :: {{markup/tty|Fetching gem metadata from https://rubygems.org/...........}} :: {{markup/tty|Fetching version metadata from https://rubygems.org/...}} :: {{markup/tty|Fetching dependency metadata from https://rubygems.org/..}} :: {{markup/tty|Fetching rake 12.3.0}} <pre> Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run: bundle install --path vendor/bundle to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo. Password: </pre> Decided this was not the way to do it, and logged in as root: : {{markup/tty|root@tootcat:~#| gem install bundler}} :: {{markup/tty|Fetching: bundler-1.16.1.gem (100%)}} :: {{markup/tty|Successfully installed bundler-1.16.1}} :: {{markup/tty|Parsing documentation for bundler-1.16.1}} :: {{markup/tty|Installing ri documentation for bundler-1.16.1}} :: {{markup/tty|Done installing documentation for bundler after 9 seconds}} :: {{markup/tty|1 gem installed}} : {{markup/tty|root@tootcat:~#| bundle install --deployment --without development test}} :: {{markup/tty/color|orange|Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.}} :: {{markup/tty/color|red|Could not locate Gemfile}} Okay, so I guess it's back to the mastodon user... : {{markup/tty|tootcat@tootcat:~/web/mastodon$| bundle install --deployment --without development test}} :: This seemed to work: [[/paste/2018/01/14/01]] : {{markup/tty|tootcat@tootcat:~/web/mastodon$ yarn install --pure-lockfile}} :: This also seemed successful, but it also asked me to upgrade Yarn with these specific commands: : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm upgrade --global yarn}} : {{markup/tty|tootcat@tootcat:~/web/mastodon$ npm rebuild node-sass}} <pre> > node-sass@4.7.2 install /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/install.js node-sass build Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node > node-sass@4.7.2 postinstall /home/tootcat/web/mastodon/node_modules/node-sass > node scripts/build.js Binary found at /home/tootcat/web/mastodon/node_modules/node-sass/vendor/linux-x64-57/binding.node Testing binary Binary is fine node-sass@4.7.2 /home/tootcat/web/mastodon/node_modules/node-sass </pre> ...and then we move on to configuring Postgres (already done) and nginx, which I think I should add as step 5. ===step 5: configure nginx - ABANDONED for now=== I made a copy of /etc/nginx/sites-available/default and called it toot-cat-new, then changed just a couple of things: * The '''server_name''' was changed from <code>toot.cat</code> to <code>new.toot.cat</code> in two places. ...and then I realized that this plan was going to require setting up extra instances of Puma and the media server (name?) on different ports from 3000 and 4000... which I think I know how to do, but this kinda crosses a threshold into territory uncertain enough that I decided to let a professional do it this time, and live to fight another day. 0ece54db72df25bed5a8ef25bc67393e5daf4a7f 10 176 575 574 2022-11-20T17:56:48Z Woozle 1 7 revisions imported: moved from HTYP wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 583 575 2022-11-20T17:58:24Z Woozle 1 Woozle moved page [[Faint]] to [[Template:Faint]] without leaving a redirect: intended namespace wikitext text/x-wiki <span style="color: #7f7f7f;">{{{1}}}</span> 1cb8e2a81c72d57435904a0b1a5b728e7cbdbf00 10 177 578 577 2022-11-20T17:56:49Z Woozle 1 2 revisions imported: moved from HTYP wikitext text/x-wiki <code>{{faint|{{{1}}}}}<span style="color:green; font-weight:bold;">{{{2|}}}</span></code> 32d030796941c97ed9d9e1618db8974687733031 582 578 2022-11-20T17:58:03Z Woozle 1 Woozle moved page [[Markup/tty]] to [[Template:Markup/tty]] without leaving a redirect: intended namespace wikitext text/x-wiki <code>{{faint|{{{1}}}}}<span style="color:green; font-weight:bold;">{{{2|}}}</span></code> 32d030796941c97ed9d9e1618db8974687733031 10 178 580 579 2022-11-20T17:56:49Z Woozle 1 1 revision imported: moved from HTYP wikitext text/x-wiki <code style="color:{{{1}}}">{{{2}}}</code> a8340135190b70537603ddb32f2ac05702993d9f 581 580 2022-11-20T17:57:39Z Woozle 1 Woozle moved page [[Markup/tty/color]] to [[Template:Markup/tty/color]] without leaving a redirect: intended namespace wikitext text/x-wiki <code style="color:{{{1}}}">{{{2}}}</code> a8340135190b70537603ddb32f2ac05702993d9f 0 67 596 361 2022-11-20T18:15:13Z Woozle 1 wikitext text/x-wiki {{page/date|nav=[[2019/02/10|prev]] .. [[2020/03/31|today]] .. [[2022/11/08|next]] }} * '''19:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''19:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''20:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. * '''20:35''' Snapshot done; resizing. "Resizing can take up to 1 minute per GB of data used by your Droplet." We've got a mostly-full 80 GB drive to resize with, so about an hour. * '''21:02''' [https://toot.cat/@woozle/103920629656934017 Back online!] de9b2e45ce263f3ac0f950514b01198b70d3d96c 597 596 2022-11-20T18:16:13Z Woozle 1 Woozle moved page [[2020-03-31]] to [[2020/03/31]] without leaving a redirect: canonical naming wikitext text/x-wiki {{page/date|nav=[[2019/02/10|prev]] .. [[2020/03/31|today]] .. [[2022/11/08|next]] }} * '''19:41''' I'll be taking toot.cat down for a major upgrade in just a couple of minutes. Watch this space for any status changes. * '''19:51''' Server is shut down. Taking a snapshot because I'm paranoid about not being able to fix things quickly if something doesn't work after the resize. It's never happened yet, but the one time I ''don't'' do it is the time when it will happen. The message said it could take "up to an hour depending on the size of your hard drive", ocelot. :-E ...sorry about that. ** We're probably going to move over to ash's server soon, but I need to set up a home system running zfs so we can do instantaneous snapshots. This upgrade is a temporary fix to deal with the higher loads we've apparently been experiencing. * '''20:24''' Snapshot looks to be about 3/4 done (why the heck doesn't DigitalOcean give a percent and an ETA?) After this, I have to resize the disk, which will probably take about as long again. * '''20:35''' Snapshot done; resizing. "Resizing can take up to 1 minute per GB of data used by your Droplet." We've got a mostly-full 80 GB drive to resize with, so about an hour. * '''21:02''' [https://toot.cat/@woozle/103920629656934017 Back online!] de9b2e45ce263f3ac0f950514b01198b70d3d96c 0 1 598 489 2022-11-20T18:17:50Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''Mew''' is a community wiki<ref name=other /> for the {{l/pub|Mastoverse}}, with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''{{l/pub|toot.cat}}''', and we have started a '''{{l/pub|cat|directory of cat-related things}}''' on the fediverse. We also offer space for Catalonian/Catalan interests, in order to help satisfy the {{l/pub|.cat}} TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Old Site News== * '''[[2020/03/31]]''' <s>site</s> TootCat going down for an upgrade * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the {{l/pub|TootCave}} to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[htyp:User:Woozle/toot.cat/2018/05/20|HTYP]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently {{l/pub|mastodon.cloud}} has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has {{l/pub|instance.business}}. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with {{l/pub|Mastodon}} design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** {{l/pub|witches.town}} goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of {{l/pub|kitty.town}} posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it [https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]. * '''2018-04-02''' The sysop of {{l/pub|witches.town}} announced that the site will be shutting down on April 30. ==Footnotes== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 51cf1ea7c151972e51144c323fd78a3f44d30890 614 598 2022-11-20T19:18:28Z Woozle 1 moved old news sections to [[2018]] wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''Mew''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 4ba1d45ce855bb4d8b5c5023845bb8f08d4c33d6 615 614 2022-11-20T19:19:43Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''MeW''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe ** [[woozle/malusers]]: list of fediverse trolls, ideologues, and jerks ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> f8c7cbb13c7cdb700d76ee0054fe657a286e653c 0 83 600 320 2022-11-20T18:20:38Z Woozle 1 nav wikitext text/x-wiki {{page/date|nav=[[2020/03/31|prev]] .. [[2022/11/08|today]] .. [[2022/11/09|next]] }} Today has been a mess of interruptions so I didn't get much chance to work on the issues, but here's a quick summary of where we are: * images sometimes will upload, but sometimes take effectively forever * This ''may'' be due to needing an upgrade; see [https://toot.cat/@clarfonthey/109310137891163841 clar fon's post]. * Doing a site upgrade was already high on my priority queue; it's now the main thing. * The obstacle, however, is that the failsafe upgrade script set up for me by ghost!admin isn't working. * That script is written in {{l/wp|Nix (package manager)|Nix}} (the entire site is now running under {{L/wp|NixOS}}), so in order to debug it I need to understand a bit more about Nix. I put the tech stuff in a subpage: [[/Nix issue]] ==Funds== * The server ''was'' costing $48/mo (DigitalOcean). * Last night, I doubled the CPU and RAM (to 8vCPUs, 16 GB RAM); we're now burning $96/mo, as long as I keep it at that level. ** It's not actually clear how much it helped. I'll have more data to look at after a day or two. The queue was getting longer all this afternoon, after having gotten almost cleared this morning. * I'm not sure exactly what the current revenue is. ** A lot of new donations came in over the past week; I'm not sure what portion were one-time. ** Prior to this week, monthly revenue was somewhere around $80-110. If that keeps up, then we go from "having a little extra for personal support" to "maybe breaking even". ** I... should probably talk about my [family's/personal] financial situation at some point, but that gets complicated. TLDR: overworked, underfunded, unemployed. * Yes, I do plan to do some fundraising -- but I kind of want to [https://toot.cat/@woozle/109310543266479370 fix things first]. cb0b001ad8b96b185523c7a58ad986c94ba9a4b4 0 89 605 506 2022-11-20T19:01:53Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2022-11-20 P.M.''' Viv completed the upgrade and restored our custom icon yesterday.|Up next: documenting/smoothing the upgrade process, so specialized knowledge is not required.}} 47566a107f98ce9e7442e0c56388f7e21a90c126 14 179 612 2022-11-20T19:10:35Z Woozle 1 Created page with "things that happened in 2018" wikitext text/x-wiki things that happened in 2018 2d237d5d89576c02f7e22d330d804635290bdd94 0 180 613 2022-11-20T19:17:39Z Woozle 1 Created page with "[[category:2018]] ==Site News== * '''[[2020/03/31]]''' <s>site</s> TootCat going down for an upgrade * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domai..." wikitext text/x-wiki [[category:2018]] ==Site News== * '''[[2020/03/31]]''' <s>site</s> TootCat going down for an upgrade * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the [[TootCave]] to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[2018/05/20]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently [[mastodon.cloud]] has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has [[instance.business]]. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with [[Mastodon]] design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** [[witches.town]] goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of [[kitty.town]] posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it <s>[https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]</s>. * '''2018-04-02''' The sysop of [[witches.town]] announced that the site will be shutting down on April 30. 54018298d2854eaeef0c6b44286ce319e492e0c6 6 181 617 616 2022-11-20T19:41:29Z Woozle 1 1 revision imported: moving from HTYP wikitext text/x-wiki [[category:screenshots]] * '''what''': screenshot of Dotster domain transfer tab while trying to (again) enter auth code for toot.cat 865b411657b7f79c62b1ccdf014375fcccfa8826 618 617 2022-11-20T19:44:34Z Woozle 1 Woozle uploaded [[File:Screenshot-2017-12-31 Dotster - DomainCentral.png]] wikitext text/x-wiki [[category:screenshots]] * '''what''': screenshot of Dotster domain transfer tab while trying to (again) enter auth code for toot.cat 865b411657b7f79c62b1ccdf014375fcccfa8826 619 618 2022-11-20T19:46:40Z Woozle 1 wikitext text/x-wiki [[category:screenshot]] [[category:TootCat]] {{c/date|2017/12/31}} * '''what''': screenshot of Dotster domain transfer tab while trying to (again) enter auth code for toot.cat 6f8a8dfc54358d0c0e4776c00375db303cf7ec3c 0 182 620 2022-11-20T19:49:33Z Woozle 1 Created page with "==Site News== * '''[[2020/03/31]]''' <s>site</s> TootCat going down for an upgrade" wikitext text/x-wiki ==Site News== * '''[[2020/03/31]]''' <s>site</s> TootCat going down for an upgrade 25eb070357212617d29ff41368b7b218624dc1c8 621 620 2022-11-20T19:49:59Z Woozle 1 wikitext text/x-wiki [[category:2020]] [[category:TootCat]] ==Site News== * '''[[2020/03/31]]''' <s>site</s> TootCat going down for an upgrade c1e40b0bc3888000ffe4f1ed9b1fad7eaa419e61 0 183 622 2022-11-20T19:51:27Z Woozle 1 Created page with "[[category:2018]] [[category:TootCat]] ==Site News== * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and..." wikitext text/x-wiki [[category:2018]] [[category:TootCat]] ==Site News== * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the [[TootCave]] to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[2018/05/20]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. * '''2018-01-02''' Dotster finally sorts out that they cannot handle [[.cat]] domains 167660dd4a9e49a1376d7b40d1aa5964c4dd5b97 626 622 2022-11-20T19:55:24Z Woozle 1 wikitext text/x-wiki [[category:2018]] [[category:TootCat]] ==Site News== * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the [[TootCave]] to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[2018/05/20]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. * '''2018-01-02''' Dotster finally sorts out that they cannot handle [[.cat]] domains ===undated=== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) 1364280b03b8f01a037599e688235563da3414b1 628 626 2022-11-20T20:02:01Z Woozle 1 wikitext text/x-wiki [[category:2018]] [[category:TootCat]] ==Site News== [[File:Screenshot-2017-12-31 Dotster - DomainCentral.png|thumb|Dotster fail - it took several days to establish that they can't handle [[.cat]] domains]] * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the [[TootCave]] to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[2018/05/20]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. * '''2018-01-02''' Dotster finally sorts out that they cannot handle [[.cat]] domains '''previous''': {{l/same|2017}} ===undated=== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) cd4b5d7527c93569a5dd0c13ba5535606acbf9cd 629 628 2022-11-20T20:02:27Z Woozle 1 wikitext text/x-wiki [[category:2018]] [[category:TootCat]] ==Site News== [[File:Screenshot-2017-12-31 Dotster - DomainCentral.png|thumb|Dotster fail - it took several days to establish that they can't handle [[.cat]] domains]] * '''2018-10-11''' <s>We now have a Hubzilla instance online at {{ls/domain|hub.toot.cat}}! It federates with Mastodon and Diaspora.</s> Borked by an upgrade; haven't had time to fix. * '''2018-08-15''' We've upgraded from Ubuntu 16.04 to 18.04, compiled Ruby with jemalloc for improved performance, and also upgraded to the latest Mastodon. ** Apparently its the Gems that take most of the time. ** Also, {{l/mastodon|kity|toot.cat}} did all the work and has rejoined the TootCat team after a prolonged absence. * '''2018-07-25''' We've had more waves of spambot registrations -- yesterday morning and this morning. SOP seems to be handling the problem. It would be nice if we could set a toggle to auto-silence new users during these attacks, because doing it by hand is time-consuming and also allows them a window of attack (which, fortunately, they aren't good at exploiting) between when they register and when I notice it. * '''2018-06-02''' The last new spambot account was recorded at 1:20pm (probably EDST) on this day. They stopped quite abruptly. * '''2018-05-30''' The SSL certificate failed to renew on the new server. [https://htyp.org/User:Woozle/toot.cat/2018/05/30 Four hours later], I fixed it. * '''2018-05-22''' spambots began creating accounts on toot.cat; we soon implemented a policy of immediately suspending any of these that tooted spam links, and silencing the rest. ** There were a few dozen accounts created as of evening the next day. * '''2018-05-20''' ** '''13:23 ET''' A long-overdue server reboot resulted in all message windows being depopulated. I retreated to the [[TootCave]] to focus on the problem. ** '''13:39 ET''' It turned out to be a misconfiguration in Nginx, and I don't know why it was even working before. See [[2018/05/20]] for details. * '''2018-05-03''' Email issues fixed. There nonetheless seems to be a [https://github.com/tootsuite/mastodon/issues/7323 deficit in Mastodon diagnostics]. * '''2018-05-01''' [https://rm.vbz.net/issues/97 Ongoing email issues] are making me tear my hair out. (How appropriate for May Day!) * '''2018-04-26''' ** Toot.Cat is [https://toot.cat/@news/99926209120865436 successfully migrated] to a new server and the latest version of Mastodon. ** [https://toot.cat/@news/99926216010193182 LottieVixen joins TootCat] as sysadmin * '''2018-04-16''': working on upgrade and migration * '''2018-01-25''': Mastodon software is up-to-date with no major issues. * '''2018-01-02''' Dotster finally sorts out that they cannot handle [[.cat]] domains '''older''': {{l/same|2017}} ===undated=== * <s>We also operate a Hubzilla instance at {{ls/domain|hub.toot.cat}}.</s> as of January 2021, this is having issues and is unusable. * @LottieVixen joined the admin team sometime in the early weeks of 2018, and did excellent work migrating (from the original server image set up by the founding team) to a new system. (Lottie is still an admin but is not currently active as a mod as of late 2020.) * @kity (formerly @ashkitten) rejoined the team (this time as an admin, having been only a moderator previously) in mid-August, and performed a lot of upgrade-and-optimization work in a very short span of time. (ash is still a mod but is taking an extended hiatus from the fediverse as of late 2020.) d0040a268c6aa0949513f8c6e2a5df4de6b53417 0 184 623 2022-11-20T19:51:53Z Woozle 1 Created page with "[[category:2017]] [[category:TootCat]] File:Screenshot-2017-12-31 Dotster - DomainCentral.png|thumb|Dotster fail - it took several days to establish that they can't handle [..." wikitext text/x-wiki [[category:2017]] [[category:TootCat]] [[File:Screenshot-2017-12-31 Dotster - DomainCentral.png|thumb|Dotster fail - it took several days to establish that they can't handle [[.cat]] domains]] * '''2017-12-30'''? auto-renewal of {{l/htyp|Let's Encrypt}} {{l/htyp|SSL}} certificate fails for unknown reasons * '''2017-12-31''' server image [https://toot.cat/@woozle/4107657 successfully transferred] to Woozle's control, and Briar Rose repoints the domain ** Woozle attempts to transfer domain to Dotster continued in [[../2018]] 80097b1c6b3699db522435fc6b2021993a8abb9a 630 623 2022-11-20T20:03:26Z Woozle 1 wikitext text/x-wiki [[category:2017]] [[category:TootCat]] '''newer''': {{l/same|2018}} * '''2017-12-31''' server image [https://toot.cat/@woozle/4107657 successfully transferred] to Woozle's control, and Briar Rose repoints the domain ** Woozle attempts to transfer domain to Dotster * '''2017-12-30'''? auto-renewal of {{l/htyp|Let's Encrypt}} {{l/htyp|SSL}} certificate fails for unknown reasons 2be57998c73a53ac30b5d81e3530e0bece99e20e 14 185 624 2022-11-20T19:52:57Z Woozle 1 Created page with "pages directly relating to [[toot.cat]]" wikitext text/x-wiki pages directly relating to [[toot.cat]] 7e59e937fa14c6cb4c159db8f7278fa1268fa69f 0 180 625 613 2022-11-20T19:54:15Z Woozle 1 moved site news to archive page wikitext text/x-wiki [[category:2018]] ==Mastodon News== * '''2018-07-03''' The #ForkTogether project now has [https://forktogether.space/mw/Main_Page a wiki]. * '''2018-06-02''' ** Apparently [[mastodon.cloud]] has been down for over a week, a new toot.cat user [https://toot.cat/@RefurioAnachro/100134355499771070 reports]. So has [[instance.business]]. I've [https://toot.cat/@woozle/100135333273070380 inquired]. ** A lot of anger and resentment has brewed between Gargron and marginalized users over issues with [[Mastodon]] design and governance. * '''2018-04-30''' ** Sina of cutie.space [https://cutie.space/@sina/99947742204242184 announced] ([https://toot.cat/web/statuses/99947747955744248 cache]) that she will no longer be serving Mastodon from that domain, effective within a matter of hours, due to a decline in users, and will be [https://cutie.space/@sina/99947969008936246 replacing it] ([https://toot.cat/web/statuses/99947972279440819 cache)] with something less resource-intensive. ** [[witches.town]] goes offline ** Woozle [https://toot.cat/@woozle/99948990608920382 posts a reassurance] that toot.cat will not be going away anytime soon. * '''2018-04-27''' Ginny McQueen of [[kitty.town]] posted [https://medium.com/@GinnyMcQueen/im-going-to-die-and-it-s-your-fault-5723a63dcefd on Medium] asking for help; Woozle posted about it <s>[https://plus.google.com/+WoozleHypertwin/posts/CzRZzofX2Y1 on Google+]</s>. * '''2018-04-02''' The sysop of [[witches.town]] announced that the site will be shutting down on April 30. 0d99add0d9f9ca819fbd150fe4dfdb58142a688c 0 48 627 426 2022-11-20T19:58:16Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. * 2022: ** Viv has been massively helpful getting things upgraded. ** ash converted the server to NixOS, and created a failsafe deployment script. * 2020: Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Archives== * [[/2020]] * [[/2018]] * [[/2017]] 0a121fdea90f826683cd038ee9f2d7fa4036697b 639 627 2022-11-24T01:50:59Z Woozle 1 /* Information */ wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. * 2022: ** Viv has been massively helpful getting things upgraded. ** ash converted the server to NixOS, and created a failsafe deployment script. * 2020: Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics * technical: [[/DNS]] ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Archives== * [[/2020]] * [[/2018]] * [[/2017]] 4ba663ce4e52fe96c820eb65223675ba84283c2b 0 164 631 513 2022-11-21T13:22:24Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:problematic]] * '''site''': https://journa.host [[journa.host]] (JH) [https://journa.host/@info/109372514074976879 suspended] two users, stating that {{fmt/quote|One published several posts attacking the integrity of another, who is a moderator on the server. The second user published a post demeaning the professionalism of a journalist, based on their identity.}} The critic was Parker Molloy, and the criticized admin is one Mike Pesca. What JH did not note is that the first one had published transmisic content, and the second one had called that into question. ==2022-11-21== * [https://retro.social/@ajroach42/109377815959702190 retro.social has silenced them]. ==2022-11-20== * [https://masto.ai/@parkermolloy/109377879615134816 Parker Molloy] defends JH, urges not blocking them ** Other users have noted that something should still be done about Mike Pesca, though. ==2022-11-19== This seems like a classic example of journalistic "both sides"ing. Much criticism ensued (saving links in case the original post is deleted, making them hard to find): * https://artisan.chat/@Curator/109372833092319826 * https://eightpoint.app/@naebumaye/109373097757641673 * https://mastodon.lol/@littletranspunk/109372845075445910 * https://kolektiva.social/@estrapade/109372874668095616 * https://mastodon.social/@MrJM/109372896735323733 - apparently the moderator is known bigot Mike Pesca * https://kolektiva.social/@nullillx/109372909921526012 * https://kolektiva.social/@maegrenofwithy/109372918108069150 * https://chaos.social/@Aphrodite/109373049184169062 * https://eightpoint.app/@Slaanesh/109372928654632387 * https://eightpoint.app/@kittenbitten/109373107104840720 * https://mstdn.social/@ostrich/109372933981211984 * https://teh.entar.net/@spacehobo/109372958258454893 * https://jorts.horse/@ancient_catbus/109372951869232369 * https://jorts.horse/@ancient_catbus/109373061197910794 * https://orbsafe.masto.host/@edclayand/109373274397268512 * https://orbsafe.masto.host/@edclayand/109373305266712231 * https://toot.community/@jimmyrayreid/109372980266604486 * https://mastodon.social/@bryceyoungquist/109373030682680647 * https://jorts.horse/@ancient_catbus/109373213182248265 * https://eightpoint.app/@rozietoez/109373006839076570 * https://eightpoint.app/@kittenbitten/109373114563174910 * https://dresden.network/@catherina/109373050489240975 * https://jorts.horse/@peptostate/109373090803125817 * https://eldritch.cafe/@getdizzy/109373106126382630 * https://writing.exchange/@XanIndigo/109373191302823221 * https://cybre.space/@asmallteapot/109373215222120706 * https://mstdn.social/@leahmcelrath/109373401849200070 * https://todon.nl/@joenepraat/109373441448198360 - screenshot showing journa.host's "no transphobia" policy b612b96dbea186cbd88dba667b20d7b00b4fff26 12 27 632 296 2022-11-21T17:18:54Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat, there are several ways: <!-- ==Money== --> * '''TootCat''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** '''Buy my stuff!''' *** muzicks: [https://woozalia.bandcamp.com/ Bandcamp] **** also on Evil Platforms&trade;: [https://www.amazon.com/Rough-Draughts-Woozalia/dp/B07S1DG25W/ref=sr_1_1?keywords=Woozalia&qid=1558612080&s=gateway&sr=8-1 Amazon Music], [https://play.google.com/store/music/album/Woozalia_Rough_Draughts?id=Bh5cfe3ltkb6v2mosqsy4bgrfh4 Google Play], [https://music.apple.com/us/album/rough-draughts/1464246974 iTunes/Apple Music], [https://open.spotify.com/album/0tLAb23QWgEgZehktIvgcH?si=qyMBbcfGSOWWmGFOQU7PYg Spotify], [https://www.youtube.com/watch?v=YW3A2egQB5A&list=PLvxUl1l3W9mpMu-ftOsBcDqtNSNm4KTaD YouTube] *** graphical merch: [https://woozalia.myspreadshop.com/ SpreadShop] (trans-related), [https://www.zazzle.com/store/woozalia Zazzle] (more political) I even accept checks (which still exist, somehow!): : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 <!-- ==Resources== We need to maintain a wish-list... * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) --> 8eacfd5c20c93ba1e08d2cf05f3c9b8ee3f6b0ff 633 632 2022-11-21T17:20:33Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat, there are several ways: <!-- ==Money== --> * '''TootCat''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** '''Buy my stuff!''' *** muzicks: [https://woozalia.bandcamp.com/ Bandcamp] **** also on Evil Platforms&trade;: [https://www.amazon.com/Rough-Draughts-Woozalia/dp/B07S1DG25W/ref=sr_1_1?keywords=Woozalia&qid=1558612080&s=gateway&sr=8-1 Amazon Music], [https://play.google.com/store/music/album/Woozalia_Rough_Draughts?id=Bh5cfe3ltkb6v2mosqsy4bgrfh4 Google Play], [https://music.apple.com/us/album/rough-draughts/1464246974 iTunes/Apple Music], [https://open.spotify.com/album/0tLAb23QWgEgZehktIvgcH?si=qyMBbcfGSOWWmGFOQU7PYg Spotify], [https://www.youtube.com/watch?v=YW3A2egQB5A&list=PLvxUl1l3W9mpMu-ftOsBcDqtNSNm4KTaD YouTube] *** graphical merch: [https://woozalia.myspreadshop.com/ SpreadShop] (trans-related), [https://www.zazzle.com/store/woozalia Zazzle] (more political) (Please [https://toot.cat/@woozle let me know] if any of the merch/music links stop working.) I even accept checks (which still exist, somehow!): : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 <!-- ==Resources== We need to maintain a wish-list... * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) --> dc52af326cbba2c8e582c3b0e27fec2efbaa3169 6 186 634 2022-11-23T00:14:32Z Woozle 1 [[category:screenshot]] * '''what''': screenshot of [[infosec.exchange]] announcing that CISA will be creating an account there wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': screenshot of [[infosec.exchange]] announcing that CISA will be creating an account there 9d85ba5484d1f2466eae1d9e1620d794e930a28e 0 187 635 2022-11-23T00:15:49Z Woozle 1 Created page with "[[category:instance]] [[category:problematic]] [[File:2022-11-22.screen.infosec.exchange.CISA.png|thumb|screenshot of the CISA announcement]] [[infosec.exchange]] is an instan..." wikitext text/x-wiki [[category:instance]] [[category:problematic]] [[File:2022-11-22.screen.infosec.exchange.CISA.png|thumb|screenshot of the CISA announcement]] [[infosec.exchange]] is an instance on the ActivityPub fediverse which allows the presence of {{l/wp|Cybersecurity and Infrastructure Security Agency|CISA}}, a US "Homeland Security" agency. Because of this, many other instances are defederating from them, and TootCat tentatively plans to follow suit. * '''2022-11-22''' [https://scholar.social/@researchfairy/109390185338133412 scholar.social/@researchfairy]: {{fmt/quote|It took ~ 35 mins for users on infosec.exchange to start sending us harassing messages}} after S.S briefly re-federated with I.E to allow a user to migrate there. eec7d9f9db76807bf39d5918c95143443f1242ab 642 635 2022-11-30T13:10:15Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:silenced]] [[File:2022-11-22.screen.infosec.exchange.CISA.png|thumb|screenshot of the CISA announcement]] [[infosec.exchange]] is an instance on the ActivityPub fediverse which allows the presence of {{l/wp|Cybersecurity and Infrastructure Security Agency|CISA}}, a US "Homeland Security" agency. Because of this, many other instances are defederating from them, and TootCat decided on 2022-11-23 to invoke a silence on 11/30 so as to give users a chance to do any migration or following that would not be possible afterwards. ==Incidents== * '''2022-11-22''' [https://scholar.social/@researchfairy/109390185338133412 scholar.social/@researchfairy]: {{fmt/quote|It took ~ 35 mins for users on infosec.exchange to start sending us harassing messages}} after S.S briefly re-federated with I.E to allow a user to migrate there. (There is additional discussion in the thread.) 46ca8363d250c30cb39b4fbddb2685a8e17066f1 643 642 2022-11-30T13:23:52Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:silenced]] [[File:2022-11-22.screen.infosec.exchange.CISA.png|thumb|screenshot of the CISA announcement]] [[infosec.exchange]] is an instance on the ActivityPub fediverse which allows the presence of {{l/wp|Cybersecurity and Infrastructure Security Agency|CISA}}, a US "Homeland Security" agency. Because of this, many other instances are defederating from them, and TootCat decided on 2022-11-23 to invoke a silence on 11/30 so as to give users a chance to do any migration or following that would not be possible afterwards. ==Incidents== * '''2022-11-22''' [https://scholar.social/@researchfairy/109390185338133412 scholar.social/@researchfairy]: {{fmt/quote|It took ~ 35 mins for users on infosec.exchange to start sending us harassing messages}} after S.S briefly re-federated with I.E to allow a user to migrate there. (There is additional discussion in the thread.) ==Discussion== * '''2022-11-30''' [https://toot.cat/@woozle/109432963342361636 @woozle] discusses the core issue and options for resolving it 59592e91f10bb7635dae9938aa65b0911d084ddc 644 643 2022-11-30T13:41:18Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:silenced]] [[File:2022-11-22.screen.infosec.exchange.CISA.png|thumb|screenshot of the CISA announcement]] [[infosec.exchange]] is an instance on the ActivityPub fediverse which allows the presence of {{l/wp|Cybersecurity and Infrastructure Security Agency|CISA}}, a US "Homeland Security" agency. Because of this, many other instances are defederating from them, and TootCat decided on 2022-11-23 to invoke a silence on 11/30 so as to give users a chance to do any migration or following that would not be possible afterwards. ==Incidents== * '''2022-11-22''' [https://scholar.social/@researchfairy/109390185338133412 scholar.social/@researchfairy]: {{fmt/quote|It took ~ 35 mins for users on infosec.exchange to start sending us harassing messages}} after S.S briefly re-federated with I.E to allow a user to migrate there. (There is additional discussion in the thread.) ==Discussion== * '''2022-11-30''' [https://toot.cat/@woozle/109432963342361636 @woozle] discusses the core issue and options for resolving it * '''2022-11-30''' [https://toot.cat/@dredmorbius/109430938419804304 @dredmorbius] asks: {{fmt/quote|@jerry Checking my understanding: CISA is an informational and advisory agency, not an intelligence agency per se. / It principally advises US organisations (commercial, governmental, and others) on practices and risks. It may have some monitoring elements. What it is not so far as I can tell is a surveillance or law enforcement entity. Though it does operate under the Dept. of Homeland Security. / As such, rationale for silencing an instance based on hosting CISA accounts seems ... questionable.}} 6d3ae4cf3b2f381bb4d80a2235a52a59b5182915 647 644 2022-12-01T01:01:27Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:silenced]] [[File:2022-11-22.screen.infosec.exchange.CISA.png|thumb|screenshot of the CISA announcement]] [[infosec.exchange]] is an instance on the ActivityPub fediverse which allows the presence of {{l/wp|Cybersecurity and Infrastructure Security Agency|CISA}}, a US "Homeland Security" agency. Because of this, many other instances are defederating from them, and TootCat decided on 2022-11-23 to invoke a silence on 11/30 so as to give users a chance to do any migration or following that would not be possible afterwards. ==Incidents== * '''2022-11-22''' ** [https://social.polymerwitch.com/@polymerwitch/109388193302230207 social.polymerwitch.com/@polymerwitch] {{fmt/quote|My decision to block them and to call for more to as well will likely have serious professional repercussions for myself. However, this is an ACAB account, and the community I have here is one where "spot the fed" actually means something. / No feds on the fediverse.}} I'm not sure that's a sustainable policy... but I can see keeping them out of ''some corners'' of fedi, at least. ** [https://scholar.social/@researchfairy/109390185338133412 scholar.social/@researchfairy]: {{fmt/quote|It took ~ 35 mins for users on infosec.exchange to start sending us harassing messages}} after S.S briefly re-federated with I.E to allow a user to migrate there. (There is additional discussion in the thread.) ==Discussion== * '''2022-11-30''' [https://toot.cat/@woozle/109432963342361636 @woozle] discusses the core issue and options for resolving it * '''2022-11-30''' [https://toot.cat/@dredmorbius/109430938419804304 @dredmorbius] asks: {{fmt/quote|@jerry Checking my understanding: CISA is an informational and advisory agency, not an intelligence agency per se. / It principally advises US organisations (commercial, governmental, and others) on practices and risks. It may have some monitoring elements. What it is not so far as I can tell is a surveillance or law enforcement entity. Though it does operate under the Dept. of Homeland Security. / As such, rationale for silencing an instance based on hosting CISA accounts seems ... questionable.}} c83a1f5ecef0cfde2c5a683cb58842b943781fa2 0 188 636 2022-11-23T20:52:33Z Woozle 1 Created page with "[[category:TLD]] ==Notes== * '''2022-11-14''' [https://j3s.sh/thought/.io-domains-considered-harmful.html .io domains considered harmful] ([https://merveilles.town/@j3s/109345..." wikitext text/x-wiki [[category:TLD]] ==Notes== * '''2022-11-14''' [https://j3s.sh/thought/.io-domains-considered-harmful.html .io domains considered harmful] ([https://merveilles.town/@j3s/109345680527772802 via]): a bit of history 76f9335a9290322d8f8823048380b964dc3abcf0 0 42 637 358 2022-11-23T20:53:11Z Woozle 1 wikitext text/x-wiki [[category:TLD]] The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about [[Catalonia]] as it comes our way. * We are interested in making space for content related to Catalonia and/or [[Catalan]]. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|blob.cat}}: a [[Pleroma]] instance * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Mastodon user Sam Toland [https://social.coop/@samtoland/100152739177441119 notes] that the .cat admins used to be much stricter, but have now loosened enforcement a bit. f48d5ec3efcf6b38c701ca5d1628e9d2f0d3f9f5 0 189 638 2022-11-24T01:49:42Z Woozle 1 Created page with "I'm mainly putting this here to try and sort out why Let's Encrypt is failing on hub.toot.cat. The HTTP verification requests are being sent to 2604:a880:400:d0::1a63:2001:, w..." wikitext text/x-wiki I'm mainly putting this here to try and sort out why Let's Encrypt is failing on hub.toot.cat. The HTTP verification requests are being sent to 2604:a880:400:d0::1a63:2001:, which ''appears'' to be the correct server (cloud1)... {| class="wikitable sortable" ! name || type || value |- | *.toot.cat || AAAA || 2604:a880:400:d0::2354:2001 |- | toot.cat || AAAA || 2604:a880:400:d0::2354:2001 |- | hub.toot.cat || AAAA || 2604:a880:400:d0::1a63:2001 |- | hub.toot.cat || A || 68.183.140.54 |- | mew.toot.cat || AAAA || 2604:a880:800:a1::126e:6001 |- | mew.toot.cat || A || 165.227.176.23 |- | toot.cat || A || 143.244.160.92 |- | *.toot.cat || A || 143.244.160.92 |} Servers: {| class="wikitable sortable" ! name || IPv4 || IPv6 |- | toot.cat || 143.244.160.92 || 2604:a880:400:d0::2354:2001 |- | cloud1.vbz.ovh || 68.183.140.54 || 2604:a880:400:d0::1a63:2001 |- | cloud5.vbz.ovh || 165.227.176.23 || 2604:a880:800:a1::126e:6001 |} 9afd8b30fa35da353d681593e9157ffec51b412d 6 190 640 2022-11-26T14:43:44Z Woozle 1 [[category:screenshot]] * '''what''': front page of [[genderheretics.xyz]] * '''retrieved''' 2022-11-26 wikitext text/x-wiki == Summary == [[category:screenshot]] * '''what''': front page of [[genderheretics.xyz]] * '''retrieved''' 2022-11-26 7dcb2b243b6c7a1df4dcbadc5c112470b10bb361 0 191 641 2022-11-26T14:46:16Z Woozle 1 Created page with "[[category:instance]] [[category:software:Soapbox]] [[category:blocked]] [[category:frozen fruit]] File:2022-11-26 at 09-41-52.screen.Gender Heretics.png|thumb|front page of..." wikitext text/x-wiki [[category:instance]] [[category:software:Soapbox]] [[category:blocked]] [[category:frozen fruit]] [[File:2022-11-26 at 09-41-52.screen.Gender Heretics.png|thumb|front page of [[genderheretics.xyz]]]] [[genderheretics.xyz]] is an ActivityPub instance running on the [[Soapbox]] software. As of 2022-11-26, its slogan &ndash; "Now With 41% More Misgendering!" &ndash; appears to be a joke about the trans suicide rate. TootCat has suspended them for that reason. They also appear to be a {{l/ip|freeze peach}} instance, which would also be sufficient grounds for at ''least'' a silence. From [https://genderheretics.xyz/about their "about" page]: <blockquote> What won't get you banned: :1. Hurting someone's feelings. :2. Unpopular opinions voiced respectfully. :3. Anything that can be solved by a personal block. :4. Cursing. :5. Lewd jokes. :6. A bot where all posts are unlisted. </blockquote> As with most freeze peach ideas, these may sound reasonable on the surface but actually promote abusive behavior and prevent many from being able to actually speak freely. 1ab9a71b1651b50f89c2372d760ebe22f1243852 0 69 645 404 2022-11-30T14:58:38Z Woozle 1 wikitext text/x-wiki All changes should be recorded with at least a one-line reason, preferably with links to relevant dialogue. ''see also the automated lists at https://toot.cat/about/more'' ==2022== * '''2022-05-06''' [https://shrike.club/about shrike.club]: death threat -- https://archive.ph/PetvA * '''2022-04-29''' [https://honkwerx.tech/wildgoose honkwerx.tech]: admin advocates anti-trans violence [https://honkwerx.tech/notice/AIx0k1iha00hAykXya][https://honkwerx.tech/notice/AIx0oxWYbi7DbvQAWu] ([[:File:2022-04-29 at 15-36-28.screen.wildgoose (@wildgoose@honkwerx.tech).png|screenshot]]) * '''2022-03-24''' [https://freeatlantis.com/about/more freeatlantis.com]: see [https://cwre.org/w/Woozle/2022/03/24 this CWRE post] ==2021== * '''2021-01-07''' Pieville (see [[:File:2021-01-07.screen.See what's happening - Pieville.png|this screenshot]]) * '''2021-01-06''' Liberdon, after discussion with user and a mod (also a [https://toot.cat/web/statuses/105504258670114486 poll]) ==2020== * '''2020-07-13''' ([https://toot.cat/@news/104508122890176142 post]): {{ls/domain|videos.lukesmith.xyz}} - Fascism, slurs, etc. * '''2020-07-09''' ([https://toot.cat/@news/104486195518238869 post]): ** {{ls/domain|boseburo.ddns.net}} - from the site: "This instance stands for Freedom of Speech...This instance stands against politically correctness and censorship in any form" ** {{ls/domain|scrapist.xyz}}: Reports of scraping by r000t again ** {{ls/domain|www.canberrasocial.net}} From the site: "...we do not censor based on ideas or political views," racism, queermisia, etc. ** {{ls/domain|cawfee.club}}: Queermisia, kinmisia, etc. ** {{ls/domain|kartoffel.cafe}}: Praising FSE for being "What gab.com wishes it could be," along with listing itself with fascist instances and instances containing sexual imagery of minors ** {{ls/domain|7td.org}}: Nazism, fascism, slurs, etc. * '''2020-06-19''' ([https://toot.cat/@news/104368904412542587 post]): {{ls/domain|witches.live}} - Racism, harassment ** Sysop added: didn't realize i never got this one over here, sorry * '''2020-06-15''' ([https://toot.cat/@news/104350277489246500 post]): {{ls/domain|lor.sh}} - Ableist slur in /about/more, "Respect free speech, but do not abuse it." * '''2020-06-13''' ([https://toot.cat/@news/104339715996927511 post]): ** {{ls/domain|us.tv}}: Hosted by fascist platforming company 'Epik,' "To allow people to upload their content without censorship." ** {{ls/domain|peertube.tech}} - Monetized by "...the new attention economy..." cryptocurrency, financial and cryptocurrency instance ** {{ls/domain|video.nobodyhasthe.biz}} - Nazism, etc. ** {{ls/domain|peertube.uno}} - "''[translated]''...we are not interested in censoring you for political or philosophical opinions." ** {{ls/domain|peertube.satoshishop.de}} - Instance for what appears to be a cryptocurrency clothing shop/hosting company ** {{ls/domain|tube.gnous.eu}} - "''[translated]''...any type of political video is accepted regardless of political orientation..." * '''2020-06-12''' ([https://toot.cat/@news/104333308645044294 post]): {{ls/domain|social.sphere.com.ai}} - Spam instance * '''2020-06-11''' ([https://toot.cat/@news/104328079396639335 post]): ** {{ls/domain|nnia.space}} - Pedophile instance ** {{ls/domain|icyphox.sh}} - "I care about freedom, both in software and speech. I police no opinion." ** {{ls/domain|wetfish.space}} - Hosting neckbeard.xyz admin [username: sjw] ** {{ls/domain|pleroma.comfy.moe}} - Hosting neckbeard.xyz admin [username: sjw], abandoned with registrations open ** {{ls/domain|lets.bemoe.online}} - Hosting neckbeard.xyz admin [username: sjw] * '''2020-06-08''' ([https://toot.cat/@news/104311885631689244 post]): {{ls/domain|norge.social}} - Racism, generally full of fascist content, etc. * '''2020-06-07''' ([https://toot.cat/@news/104304452030739859 post]): ** {{ls/domain|hitchhicker.social}} - Racism, {{l/ip|TERF}}, etc. ** {{ls/domain|toast.cafe}}, {{ls/domain|honk.toast.cafe}} - Ableist slur, etc. * '''2020-06-04''' ([https://toot.cat/@news/104288878877827539 post]): ** {{ls/domain|springbo.cc}} - White supremacy, etc. ** {{ls/domain|dogeposting.social}} - Fascism, white supremacy, right-wing conspiracies, etc. ** {{ls/domain|social.thisisjoes.site}} - "Freedom of speech and association are valued here." ** {{ls/domain|pleroma.jeder.pl}} - Nazi imagery [Pepe], ableism, etc. * '''2020-05-09''' ([https://toot.cat/@news/104140663565893335 post]): {{ls/domain|pl.skyn3t.in}} - Fascism, queermisia, fatmisia, ableism, imagery of assault on the marginalized, slurs, nazism, etc. * '''2020-05-02''' ([https://toot.cat/@news/104100222509664991 post]): {{ls/domain|dickkickextremist.xyz}} - Fascism * '''2020-04-30''' ([https://toot.cat/@news/104089988553642013 post]): ** {{ls/domain|udongein.xyz}} - Sexual art of minors ** {{ls/domain|smugloli.net}} - Backup domain of smuglo.li [Sexual art of minors] ** {{ls/domain|pleroma.uwah.moe}} - Queermisia * '''2020-04-26''': ** ([https://toot.cat/@news/104067161819653494 post]): {{ls/domain|raplst.town}} - Sexual assault instance (Obvious Block is obvious) ** ([https://toot.cat/@news/104065944841866454 post]): {{ls/domain|fuck-man-i-just-want-like-one-friend.xyz}} - Run by the ligma.pro admin [r000t], {{l/ip|transmisia}}, data scraping, etc. * '''2020-04-17''': ** ([https://toot.cat/@news/104016414388069361 post]): {{ls/domain|social.byoblu.com}} - Fascism, right-wing conspiracies, etc. ** ([https://toot.cat/@news/104016220466722385 post]): *** {{ls/domain|princess.cat}} - Run by a {{ls/domain|freespeechextremist.com}} user, fascism, ableism, etc. *** {{ls/domain|archivefedifor.fun}} - Run by the {{ls/domain|ligma.pro}} admin [r000t] transmisia, data scraping, etc. *** {{ls/domain|definitely-not-archivefedifor.fun}} - Run by the ligma.pro admin [r000t], transmisia, data scraping, etc. *** {{ls/domain|husk.site}} - Fascism, etc. *** <s>{{l/pub|inex.rocks}} - Defending fascism</s> lifted (provisionally) by Woozle on 2020-07-22 ** ([https://toot.cat/@news/104015379090184018 post]): {{ls/domain|neckbeard.xyz}} - Fascism, non-moderation, etc. * '''2020-03-08''' ([https://toot.cat/@news/103790468137161501 post]): ** {{ls/domain|coom.club}} - Non-moderation, queermisia, fascism, etc. ** {{ls/domain|video.autizmo.xyz}} - Ableism, non-moderation, fascism, etc. ** {{ls/domain|koyu.space}} - Defending fascists, anti-moderation ** {{ls/domain|fedi.n0id.space}} - Defending fascists, anti-moderation ** {{ls/domain|search.fedi.app}} - Followbot instance, most likely indexing ** {{ls/domain|activism.openworlds.info}} - Eugenics, non-moderation, etc. ** {{ls/domain|mastodon.hatthieves.es}} - Run by the {{ls/domain|social.hatthieves.es}} admin, mass following ** {{ls/domain|pleroma.mouse.services}} - Admin owns an account on {{ls/domain|rape.lol}} ** {{ls/domain|jaeger.website}} - Run by the {{ls/domain|jpop.club}} and {{ls/domain|hedgehoghunter.club}} admin, transmisia, non-moderation, etc. ** {{ls/domain|pleroma.com}} - Run by the admin of {{ls/domain|bikeshed.party}}, fascism, spam, etc. * '''2020-02-17''' ** ([https://toot.cat/@news/103675431800314134 post]): *** {{ls/domain|video.fediverso.net}}, {{ls/domain|fediverso.net}} - MRA, anti-feminism *** {{ls/domain|peertube.bittube.video}} - No moderation *** {{ls/domain|video.galacticstrip.com}} - "We allow to host...more controversial material as we honor freedom of speech..." *** {{ls/domain|tube.chatelet.ovh}} - No moderation *** {{ls/domain|peertube.quaylessed.icu}} - "censorship free video platform" *** {{ls/domain|tube.lain.church}} - Code of conduct links to ASCII art, no moderation *** {{ls/domain|videos.libreha.sh}} - "...there has been much anger and frustration in the crypto space regarding the apparent 'censorship' of certain blockchain influencers. Thus, we've decided to establish this instance..." ** ([https://toot.cat/@news/103675388875266656 post]): {{ls/domain|crypto-group-buy.com}} - Spam * '''2020-02-01''' ([https://toot.cat/@news/103581933295911145 post]): {{ls/domain|micca.xyz}} - Racism, transmisia, etc. * '''2020-01-28''' ([https://toot.cat/@news/103564681530561027 post]): {{ls/domain|thewired.xyz}} - Gab and FSE friendly, transmisia, etc. * '''2020-01-20''' ** ([https://toot.cat/@news/103517667729000507 post]): {{ls/domain|gameliberty.club}}, {{ls/domain|peervideo.club}}, {{ls/domain|catgirl.life}} - Nazism, racism, queermisia, ableism, sexual art of minors, harassment, etc. ** ([https://toot.cat/@news/103517317089844019 post]): *** {{ls/domain|ligma.pro}} - Transmisia, data scraping, Gab friendly, etc. *** {{ls/domain|sneak.berlin}} - Harassment, Gab friendly, possibly data scraping * '''2020-01-16''' ([https://toot.cat/@news/103495928938164845 post]): ** {{ls/domain|spinster.xyz}} - Gab instance, {{l/ip|TERF}}s (new TERF admin confirmed 2022-11-30) ** {{ls/domain|gleasonator.com}} - Soapbox instance run by a spinster.xyz admin, TERFs * '''2020-01-08''': ** ([https://toot.cat/@news/103466494343238412 post]): {{ls/domain|expired.mentality.rip}} - Ableism, Gab friendly, etc. ** ([https://toot.cat/@news/103450367325621252 post]): {{ls/domain|uwu.social}} - Fascism, transmisia, hosting Gab users, etc * '''2020-01-07''' ([https://toot.cat/@news/103445285600792381 post]) ** {{ls/domain|buckeye.social}} - Transmisia, Gab support, etc ** {{ls/domain|gamers.exposed}} - Joking about sexual assault, racism, etc 52f8564543ff6e9d8033ff1f1396fd8129880264 0 150 646 500 2022-11-30T15:18:52Z Woozle 1 /* History */ wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance with a "free speech" approach to moderation. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others" and the site had 19 users. ==Issues== While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, potentially allowing anti-science content and toxic users to proliferate. Numerous users (on and off TootCat) have brought this problem to our attention. At the present time, however, we have no specific examples of problematic posts. Using "#[https://qoto.org/tags/woke woke]" as an example of a politically-charged tag, I found mostly positive/reasonable posts and relatively few which seem problematic. (Notes: [https://qoto.org/@b_chocolatey/109329018486628722]) They do federate with [[noagendasocial.com|NoAgendaSocial]] and with [[brighteon.social]] which hosts anti-science site Natural News, and their main feed consequently does contain a small but significant quantity of right-wing BS. On [[2022/11/17]], Jeffrey Freeman (apparently the domain owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-11-30''' Freeman starts a [https://gitlab.com/ufoi United Federation of Instances] project, with high-minded-sounding [https://gitlab.com/ufoi/constitution Constitution] draft. [https://social.pixie.town/@joepie91/109433103633543373 some analysis] * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. * '''2018-12-06''' qoto.org has 2149 users<ref name=qoto-archive-8 /> * '''2018-11-07''' qoto.org has 1936 users<ref name=qoto-archive-7 /> * '''2018-10-07''' qoto.org has 1799 users<ref name=qoto-archive-6 /> * '''2018-09-02''' qoto.org has 1433 users<ref name=qoto-archive-5 /> * '''2018-08-15''' qoto.org has 112 users<ref name=qoto-archive-4 /> * '''2018-08-07''' qoto.org has 102 users<ref name=qoto-archive-3 /> * '''2018-07-10''' qoto.org has 19 users<ref name=qoto-archive-2 />; first appearance in archive.org ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-3>'''2018-08-07 archive''': [https://web.archive.org/web/20180807123948/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-4>'''2018-08-15 archive''': [https://web.archive.org/web/20180815233147/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-5>'''2018-09-02 archive''': [https://web.archive.org/web/20180902134516/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-6>'''2018-10-07 archive''': [https://web.archive.org/web/20181007173538/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-7>'''2018-11-07 archive''': [https://web.archive.org/web/20181107154717/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-8>'''2018-12-06 archive''': [https://web.archive.org/web/20181206143118/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> bbeb690d5f2a850c44ceafc2950d48a26bc50e95 655 646 2022-12-08T23:18:56Z Woozle 1 /* History */ wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] {{fmt/title|qoto.org: "Question Others to Teach Ourselves. A STEM-oriented instance."}} * '''site''': [https://qoto.org/about qoto.org] * '''status''': silenced (November 2022) ==About== [[qoto.org]] is a STEM-oriented Mastodon instance with a "free speech" approach to moderation. The domain was registered on 2008-05-31^{{{l/sub|whois}}}, long before Mastodon existed, and appears to have first been used in 2011 to present content<ref name=qoto-archive-1 /> from [[Syncleus]], Jeffrey Freeman's think-tank<ref name=syncleus-freeman-bio />. The earliest evidence of its being a Mastodon instance is in July, 2018<ref name=qoto-archive-2 />, at which time the slogan was "Question Others, Teach Others" and the site had 19 users. ==Issues== While having a lot of valid science content, they have also unfortunately chosen a "free speech" approach to moderation, potentially allowing anti-science content and toxic users to proliferate. Numerous users (on and off TootCat) have brought this problem to our attention. At the present time, however, we have no specific examples of problematic posts. Using "#[https://qoto.org/tags/woke woke]" as an example of a politically-charged tag, I found mostly positive/reasonable posts and relatively few which seem problematic. (Notes: [https://qoto.org/@b_chocolatey/109329018486628722]) They do federate with [[noagendasocial.com|NoAgendaSocial]] and with [[brighteon.social]] which hosts anti-science site Natural News, and their main feed consequently does contain a small but significant quantity of right-wing BS. On [[2022/11/17]], Jeffrey Freeman (apparently the domain owner) used a tool published by the now-defunct {{l/ip|Kiwi Farms}} online-terrorism organization to identify instances which had blocked QOTO, and sent out [[2022/11/17/QOTO|an email]] to the admins of each asking to have the block removed. The email, unfortunately, did not really address the issues, and made a number of questionable claims. ==History== * '''2022-12-08''' [https://stop.voring.me/notes/98j7helkhr stop.voring.me/@thatonecalculator] comments {{fmt/quote|#fediblock qoto.org -- for those of you who don't know, they made an organization called UFOI and tricked instance admins like me into joining, while hiding manipulative subclauses far down in their TOS.}} Includes screenshots of posts by Freeman. * '''2022-11-30''' Freeman starts a [https://gitlab.com/ufoi United Federation of Instances] project, with high-minded-sounding [https://gitlab.com/ufoi/constitution Constitution] draft. [https://social.pixie.town/@joepie91/109433103633543373 some analysis] * '''2022-11-17''' [[2022/11/17/QOTO|email from QOTO]] sent to numerous instances, requesting lift of limitations * '''2022-11-12''' On request from a new user, [https://toot.cat/@woozle/109331146818085671 this was changed] from block to silence. * '''2022-11-??''' Instance suspended. "An inclusive free speech instance," transmisia, COVID-19 vaccine misinformation, etc. * '''2018-12-06''' qoto.org has 2149 users<ref name=qoto-archive-8 /> * '''2018-11-07''' qoto.org has 1936 users<ref name=qoto-archive-7 /> * '''2018-10-07''' qoto.org has 1799 users<ref name=qoto-archive-6 /> * '''2018-09-02''' qoto.org has 1433 users<ref name=qoto-archive-5 /> * '''2018-08-15''' qoto.org has 112 users<ref name=qoto-archive-4 /> * '''2018-08-07''' qoto.org has 102 users<ref name=qoto-archive-3 /> * '''2018-07-10''' qoto.org has 19 users<ref name=qoto-archive-2 />; first appearance in archive.org ==Footnotes== <references> <ref name=qoto-archive-1>'''2011-09-23 archive''': [https://web.archive.org/web/20110923131305/http://www.qoto.org/ qoto.org home page]</ref> <ref name=qoto-archive-2>'''2018-07-10 archive''': [https://web.archive.org/web/20180710004851/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-3>'''2018-08-07 archive''': [https://web.archive.org/web/20180807123948/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-4>'''2018-08-15 archive''': [https://web.archive.org/web/20180815233147/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-5>'''2018-09-02 archive''': [https://web.archive.org/web/20180902134516/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-6>'''2018-10-07 archive''': [https://web.archive.org/web/20181007173538/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-7>'''2018-11-07 archive''': [https://web.archive.org/web/20181107154717/https://qoto.org/about qoto.org about page]</ref> <ref name=qoto-archive-8>'''2018-12-06 archive''': [https://web.archive.org/web/20181206143118/https://qoto.org/about qoto.org about page]</ref> <ref name=syncleus-freeman-bio>'''2011-07-16 archive''': [https://web.archive.org/web/20110716181415/http://www.syncleus.com/about-us/our-team/ Syncleus: Our Team: Jeffrey Freeman, CTO, President, & Chairman]</ref> </references> 9d266dad0a3fa2012884c24a815e585d1da56856 0 161 648 509 2022-12-02T01:24:52Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:federated]] [[File:2022-11-19 at 20-09-41.screen.toot.community.logo-slogan.png|thumb|Site slogan: {{fmt/quote|We're a generic, free-for-all Mastodon instance hosted in The Netherlands. We're welcoming to all that seek a place of enjoyment online while being excellent to each other.}} How can you be excellent to each other while also being a free-for-all? Well, we'll see how this goes, since they did handle the Moore thing.]] * '''site''': https://toot.community * '''status''': full federation as of 2022-12-01 TootCat suspended [[toot.community]] (TComm) on [[2022/11/26]] for refusing to suspend transmisic/TERF journalist {{l/wp|Suzanne Moore}}, but apparently TComm did in fact suspend her the day after we (and many others) complained about it. Upon user inquiry I investigated the situation, discovered that the problem had been resolved, and undid the block. -W. ==Events== * '''2022-12-01''' We at TootCat promptly and immediately respond to this event of about 2 weeks ago, and reverse the suspension. * '''2022-11-15''' [https://mastodon.lol/@peterherold/109348336566879964 mastodon.lol/@peterherold] notes that Moore was suspended in response to the outcry. * '''2022-11-14''' [https://toot.cat/@news/109343526830497124 TootCat suspension announcement] 9a1c3ab504d903078a0f0daee455789f5785c0e8 6 192 649 2022-12-05T16:28:09Z Woozle 1 [[category:SVG]] [[category:diagram]] [[category:dialogue]] wikitext text/x-wiki == Summary == [[category:SVG]] [[category:diagram]] [[category:dialogue]] b60d2ec7441c70aaf0954bb2f4fe96833a270d64 0 159 650 512 2022-12-08T13:36:53Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://mastodon.scot We [https://toot.cat/@news/109343526830497124 suspended] [[mastodon.scot]] on [[2022/11/26]], for allowing a police union presence. Since then we've also had a report that they were very reluctant to suspend a transphobe, and later reports of additional transphobe presence, so that seems to validate the decision. 49372ef4a9ab344cea27fa8c2637e6445494ebfe 654 650 2022-12-08T23:15:58Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://mastodon.scot We [https://toot.cat/@news/109343526830497124 suspended] [[mastodon.scot]] on [[2022/11/26]], for allowing a police union presence (David Hamilton, chair of the Scottish Police Federation). Since then we've also had a report that they were very reluctant to suspend a transphobe, and later reports of additional transphobe presence, so that seems to validate the decision. 3d0f6def1a0f2a2b83de5bab95339eccbfce838a 0 193 651 2022-12-08T16:47:02Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==Hearsay== I have heard one allegation that this instance is antisemitic, but as of yet..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==Hearsay== I have heard one allegation that this instance is antisemitic, but as of yet have no evidence to support this. -W. f1f951faa7008ab7651b59a85665d013022866a7 653 651 2022-12-08T22:41:05Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance. The domain was first registered on 2022-10-28. ==Hearsay== I have heard one allegation that this instance is antisemitic, but as of yet have no evidence to support this. -W. b5e996e04927db7e4d83f4dfffaf18d13d1fb756 656 653 2022-12-14T20:42:44Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance. The domain was first registered on 2022-10-28. I blocked them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. e669f8d49a48bddb954a9ddedd7ad3f0be5820ba 657 656 2022-12-14T20:44:27Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I blocked them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. The domain was first registered on 2022-10-28. 92869d1e764dfd9702b75d0b4423c7969b44f4f7 658 657 2022-12-14T20:59:11Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I blocked them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. The domain was first registered on 2022-10-28. ==Discussion== * '''2022-12-13''' [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} 01ddd3f4732d6843e3a7d22867f3461d6e3f0433 10 194 652 2022-12-08T22:37:25Z Woozle 1 Created page with "{{l/ip|{{PAGENAME}}|Issuepedia}}" wikitext text/x-wiki {{l/ip|{{PAGENAME}}|Issuepedia}} f4abd0d8d7d0f3ffdd9a67d88e3a889a398f4e5c 6 195 659 2022-12-14T21:18:14Z Woozle 1 [[category:screenshot]] [[category:eightpoint.app]] {{c/date|2022-12-09}} wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint.app]] {{c/date|2022-12-09}} f030341fbfaee8a214cf552b2e1c0282cf042641 660 659 2022-12-14T21:19:12Z Woozle 1 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-09}} c3ab5a6b399036f897d54a447b7351662e43809c 6 196 661 2022-12-14T21:19:36Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-09}} wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-09}} c3ab5a6b399036f897d54a447b7351662e43809c 6 197 662 2022-12-14T21:21:03Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] [[category:archive.org]] {{c/date|2022-12-08}} wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] [[category:archive.org]] {{c/date|2022-12-08}} 1c56a4bba320e745976c37a6433c402c41ff98f1 6 198 663 2022-12-14T21:22:26Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] [[category:archive.org]] {{c/date|2022-12-07}} wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] [[category:archive.org]] {{c/date|2022-12-07}} 1e0f10523715a16242f13722717e2a27393acbb5 6 199 664 2022-12-14T21:32:51Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-04}} * '''retrieved''' from [https://web.archive.org/web/20221204054229/https://eightpoint.app/about archive.org] on 2022-12-09 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-04}} * '''retrieved''' from [https://web.archive.org/web/20221204054229/https://eightpoint.app/about archive.org] on 2022-12-09 c2692b6d22fd7e41a7f51fc95ea215ed6e305f1d 6 200 665 2022-12-14T21:34:10Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-04}} * '''retrieved''' from [https://web.archive.org/web/20221204211747/https://eightpoint.app/about archive.org] on 2022-12-09 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-12-04}} * '''retrieved''' from [https://web.archive.org/web/20221204211747/https://eightpoint.app/about archive.org] on 2022-12-09 153413a38c279f17147e4b5d3d76d523e2c5d12a 6 201 666 2022-12-14T21:36:44Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-11-20}} * '''retrieved''' from [https://web.archive.org/web/20221120044700/https://eightpoint.app/about archive.org] on 2022-12-09 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-11-20}} * '''retrieved''' from [https://web.archive.org/web/20221120044700/https://eightpoint.app/about archive.org] on 2022-12-09 20c3b22d8ef2c8a6d8f9eda30b509660ce3ab040 6 202 667 2022-12-14T21:41:29Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-11-18}} * '''retrieved''' from [https://web.archive.org/web/20221118210613/https://eightpoint.app/about archive.org] (21:06:13) on 2022-12-09 ** almost-identical page at [https://web.archive.org/web/20221118005753/https://eightpoint.app/about 00:57:53] wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-11-18}} * '''retrieved''' from [https://web.archive.org/web/20221118210613/https://eightpoint.app/about archive.org] (21:06:13) on 2022-12-09 ** almost-identical page at [https://web.archive.org/web/20221118005753/https://eightpoint.app/about 00:57:53] baa3db3479754be7306a4fa25b9329717a8b6bd4 6 203 668 2022-12-14T21:45:10Z Woozle 1 [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-11-12}} * '''retrieved''' from [https://web.archive.org/web/20221112225323/https://eightpoint.app/about archive.org] on 2022-12-09 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:eightpoint]] {{c/date|2022-11-12}} * '''retrieved''' from [https://web.archive.org/web/20221112225323/https://eightpoint.app/about archive.org] on 2022-12-09 e49d9bdf30a918c2194810eb7205383310567aaf 14 204 669 2022-12-14T21:47:53Z Woozle 1 Created page with "images and pages relating to [[eightpoint.app]]" wikitext text/x-wiki images and pages relating to [[eightpoint.app]] 4ad9f820ee36b5563b44b0d89fc144968571ed22 0 193 670 658 2022-12-14T22:29:03Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I blocked them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. ==Discussion== * '''2022-12-13''' [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} ==History== Timestamps are according to archive.org, probably UTC. * '''2022-12-09''': moderator is no "12of47", a user who also had a [https://toot.cat/@12of47 TootCat account]. The following record is not intended as criticism of that user: ** '''-12-07 19:46''': [https://toot.cat/@12of47/109475290428576687 toot.cat/@12of47] {{fmt/quote|thinkin about moving to eightpoint as our primary server. Let´s see if we can}} ** '''-12-07 21:57''': [https://toot.cat/@12of47/109475806250322119 toot.cat/@12of47] {{fmt/quote|will be spending most of our time on 12@eightpoint.app now, go follow us there, cuties}} ** '''-12-09 09:46''': [https://toot.cat/@12of47/109484255733184547 toot.cat/@12of47] {{fmt/quote|every single person who worked to get http://eightpoint.app shut down, we curse you to never find a home, to always feel fucking isolated from every space you ever exist in, to never feel safe to be yourself, as you are doing to us}} ** '''-12-09 14:08''': [https://toot.cat/@12of47/109485286007607549 toot.cat/@12of47] (three similar posts later) {{fmt/quote|we are now the new owner of http://eightpoint.app! We are fucking Kallai, and we will never die to the actions of the fash}} ** 12of47 remains admin of 8P as of 2022-12-14. * '''2022-12-07''': moderator is now "@admin" ([[:File:2022-12-07.screen.eightpoint.png|screenshot]]) ** There is no evidence that this account remained beyond 12-08. (12/07:[https://web.archive.org/web/20221207221550/https://eightpoint.app/@admin archive.org]; 12-08: [[:File:2022-12-08.screen.eightpoint.png|screenshot]]). [https://eightpoint.app/@admin Gone] as of 2022-12-14. * '''2022-11-20''' - '''-12-04''': 8P comes back online ([[:File:2022-12-04.211747.screen.eightpoint.png|12-04]]), apparently with a software upgrade ** the distinctive 8-point star logo is in the site header at [https://mew.toot.cat/wikiup/6/6b/2022-12-04.054229.screen.eightpoint.png 05:42:29] but has reverted to default Mastodon artwork by [[:File:2022-12-04.211747.screen.eightpoint.png|21:17:47]] ** moderator is now [https://eightpoint.app/@egirlterra Terra] - account exists from [https://web.archive.org/web/20221116115852/https://eightpoint.app/@egirlterra 11-16] to [https://web.archive.org/web/20221209163043/https://eightpoint.app/@egirlterra 12-09], gone as of 12-14 * '''2022-11-18''' - '''-11-20''': 8P goes offline sometime during this span ([[:File:2022-11-18.screen.eightpoint.png|11-18]], [[:File:2022-11-20.screen.eightpoint.down.png|11-20]]) * '''2022-11-12''' earliest online presence of 8P on archive.org ([[:File:2022-11-12-2253.screen.eightpoint.app.png|screenshot]]) * '''2022-10-28''' domain is first registered 85209f53dfb5d277efc13738b5aada3304d0e2f4 671 670 2022-12-14T22:49:59Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I silenced them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. ==Discussion== * '''2022-12-13''' [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} ==History== Timestamps are according to archive.org, probably UTC. * '''2022-12-09''': moderator is no "12of47", a user who also had a [https://toot.cat/@12of47 TootCat account]. The following record is not intended as criticism of that user: ** '''-12-07 19:46''': [https://toot.cat/@12of47/109475290428576687 toot.cat/@12of47] {{fmt/quote|thinkin about moving to eightpoint as our primary server. Let´s see if we can}} ** '''-12-07 21:57''': [https://toot.cat/@12of47/109475806250322119 toot.cat/@12of47] {{fmt/quote|will be spending most of our time on 12@eightpoint.app now, go follow us there, cuties}} ** '''-12-09 09:46''': [https://toot.cat/@12of47/109484255733184547 toot.cat/@12of47] {{fmt/quote|every single person who worked to get http://eightpoint.app shut down, we curse you to never find a home, to always feel fucking isolated from every space you ever exist in, to never feel safe to be yourself, as you are doing to us}} ** '''-12-09 14:08''': [https://toot.cat/@12of47/109485286007607549 toot.cat/@12of47] (three similar posts later) {{fmt/quote|we are now the new owner of http://eightpoint.app! We are fucking Kallai, and we will never die to the actions of the fash}} ** 12of47 remains admin of 8P as of 2022-12-14. * '''2022-12-07''': moderator is now "@admin" ([[:File:2022-12-07.screen.eightpoint.png|screenshot]]) ** There is no evidence that this account remained beyond 12-08. (12/07:[https://web.archive.org/web/20221207221550/https://eightpoint.app/@admin archive.org]; 12-08: [[:File:2022-12-08.screen.eightpoint.png|screenshot]]). [https://eightpoint.app/@admin Gone] as of 2022-12-14. * '''2022-11-20''' - '''-12-04''': 8P comes back online ([[:File:2022-12-04.211747.screen.eightpoint.png|12-04]]), apparently with a software upgrade ** the distinctive 8-point star logo is in the site header at [https://mew.toot.cat/wikiup/6/6b/2022-12-04.054229.screen.eightpoint.png 05:42:29] but has reverted to default Mastodon artwork by [[:File:2022-12-04.211747.screen.eightpoint.png|21:17:47]] ** moderator is now [https://eightpoint.app/@egirlterra Terra] - account exists from [https://web.archive.org/web/20221116115852/https://eightpoint.app/@egirlterra 11-16] to [https://web.archive.org/web/20221209163043/https://eightpoint.app/@egirlterra 12-09], gone as of 12-14 * '''2022-11-18''' - '''-11-20''': 8P goes offline sometime during this span ([[:File:2022-11-18.screen.eightpoint.png|11-18]], [[:File:2022-11-20.screen.eightpoint.down.png|11-20]]) * '''2022-11-12''' earliest online presence of 8P on archive.org ([[:File:2022-11-12-2253.screen.eightpoint.app.png|screenshot]]) * '''2022-10-28''' domain is first registered 06f36e11df6404f229f629f5718eb9e3158e6980 672 671 2022-12-14T22:50:25Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I silenced them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. ==Discussion== * '''2022-12-13''' [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} ==History== Timestamps are according to archive.org, probably UTC. * '''2022-12-09''': moderator is no "12of47", a user who also had a [https://toot.cat/@12of47 TootCat account]. The following record is not intended as criticism of that user: ** '''-12-07 19:46''': [https://toot.cat/@12of47/109475290428576687 toot.cat/@12of47] {{fmt/quote|thinkin about moving to eightpoint as our primary server. Let´s see if we can}} ** '''-12-07 21:57''': [https://toot.cat/@12of47/109475806250322119 toot.cat/@12of47] {{fmt/quote|will be spending most of our time on 12@eightpoint.app now, go follow us there, cuties}} ** '''-12-09 09:46''': [https://toot.cat/@12of47/109484255733184547 toot.cat/@12of47] {{fmt/quote|every single person who worked to get http://eightpoint.app shut down, we curse you to never find a home, to always feel fucking isolated from every space you ever exist in, to never feel safe to be yourself, as you are doing to us}} ** '''-12-09 14:08''': [https://toot.cat/@12of47/109485286007607549 toot.cat/@12of47] (three similar posts later) {{fmt/quote|we are now the new owner of http://eightpoint.app! We are fucking Kallai, and we will never die to the actions of the fash}} ** 12of47 remains admin of 8P as of 2022-12-14. * '''2022-12-07''': moderator is now "@admin" ([[:File:2022-12-07.screen.eightpoint.png|screenshot]]) ** There is no evidence that this account remained beyond 12-08. (12/07:[https://web.archive.org/web/20221207221550/https://eightpoint.app/@admin archive.org]; 12-08: [[:File:2022-12-08.screen.eightpoint.png|screenshot]]). [https://eightpoint.app/@admin Gone] as of 2022-12-14. * '''2022-11-20''' - '''-12-04''': 8P comes back online ([[:File:2022-12-04.211747.screen.eightpoint.png|12-04]]), apparently with a software upgrade ** the distinctive 8-point star logo is in the site header at [https://mew.toot.cat/wikiup/6/6b/2022-12-04.054229.screen.eightpoint.png 05:42:29] but has reverted to default Mastodon artwork by [[:File:2022-12-04.211747.screen.eightpoint.png|21:17:47]] ** moderator is now [https://eightpoint.app/@egirlterra Terra] - account exists from [https://web.archive.org/web/20221116115852/https://eightpoint.app/@egirlterra 11-16] to [https://web.archive.org/web/20221209163043/https://eightpoint.app/@egirlterra 12-09], gone as of 12-14 * '''2022-11-18''' - '''-11-20''': 8P goes offline sometime during this span ([[:File:2022-11-18.screen.eightpoint.png|11-18]], [[:File:2022-11-20.screen.eightpoint.down.png|11-20]]) * '''2022-11-12''' earliest online presence of 8P on archive.org ([[:File:2022-11-12-2253.screen.eightpoint.app.png|screenshot]]) * '''2022-10-28''' domain is first registered 961894bdabbd9acdf9de3c12c1f59300ebd93f8d 674 672 2022-12-15T00:05:44Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I silenced them on [https://toot.cat/@woozle/109513962788427811 2022-12-14]. ==Discussion== * '''2022-12-13''' ** [https://newsie.social/@jessothomson/109508467120794305 newsie.social/@jessothomson] {{fmt/quote|If you want to see how the eightpoint hate machine works...}} ** [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} * '''2022-11-29''' [https://kolektiva.social/@AvengingFemme/109428725810362095 kolektiva.social/@AvengingFemme: Response to Slaanesh re: "abuse apologist" posts and my position on eightpoint.app] (thread) ==History== Timestamps are according to archive.org, probably UTC. * '''2022-12-09''': moderator is no "12of47", a user who also had a [https://toot.cat/@12of47 TootCat account]. The following record is not intended as criticism of that user: ** '''-12-07 19:46''': [https://toot.cat/@12of47/109475290428576687 toot.cat/@12of47] {{fmt/quote|thinkin about moving to eightpoint as our primary server. Let´s see if we can}} ** '''-12-07 21:57''': [https://toot.cat/@12of47/109475806250322119 toot.cat/@12of47] {{fmt/quote|will be spending most of our time on 12@eightpoint.app now, go follow us there, cuties}} ** '''-12-09 09:46''': [https://toot.cat/@12of47/109484255733184547 toot.cat/@12of47] {{fmt/quote|every single person who worked to get http://eightpoint.app shut down, we curse you to never find a home, to always feel fucking isolated from every space you ever exist in, to never feel safe to be yourself, as you are doing to us}} ** '''-12-09 14:08''': [https://toot.cat/@12of47/109485286007607549 toot.cat/@12of47] (three similar posts later) {{fmt/quote|we are now the new owner of http://eightpoint.app! We are fucking Kallai, and we will never die to the actions of the fash}} ** 12of47 remains admin of 8P as of 2022-12-14. * '''2022-12-07''': moderator is now "@admin" ([[:File:2022-12-07.screen.eightpoint.png|screenshot]]) ** There is no evidence that this account remained beyond 12-08. (12/07:[https://web.archive.org/web/20221207221550/https://eightpoint.app/@admin archive.org]; 12-08: [[:File:2022-12-08.screen.eightpoint.png|screenshot]]). [https://eightpoint.app/@admin Gone] as of 2022-12-14. * '''2022-11-20''' - '''-12-04''': 8P comes back online ([[:File:2022-12-04.211747.screen.eightpoint.png|12-04]]), apparently with a software upgrade ** the distinctive 8-point star logo is in the site header at [https://mew.toot.cat/wikiup/6/6b/2022-12-04.054229.screen.eightpoint.png 05:42:29] but has reverted to default Mastodon artwork by [[:File:2022-12-04.211747.screen.eightpoint.png|21:17:47]] ** moderator is now [https://eightpoint.app/@egirlterra Terra] - account exists from [https://web.archive.org/web/20221116115852/https://eightpoint.app/@egirlterra 11-16] to [https://web.archive.org/web/20221209163043/https://eightpoint.app/@egirlterra 12-09], gone as of 12-14 * '''2022-11-18''' - '''-11-20''': 8P goes offline sometime during this span ([[:File:2022-11-18.screen.eightpoint.png|11-18]], [[:File:2022-11-20.screen.eightpoint.down.png|11-20]]) * '''2022-11-12''' earliest online presence of 8P on archive.org ([[:File:2022-11-12-2253.screen.eightpoint.app.png|screenshot]]) * '''2022-10-28''' domain is first registered 19aa958c8f8998700d2969c0e00eff3218f0e5ab 686 674 2022-12-20T21:21:46Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I silenced them on [https://toot.cat/@woozle/109513962788427811 2022.12.14]. ==Discussion== * '''2022.12.13''' ** [https://newsie.social/@jessothomson/109508467120794305 newsie.social/@jessothomson] {{fmt/quote|If you want to see how the eightpoint hate machine works...}} ** [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} * '''2022.11.29''' [https://kolektiva.social/@AvengingFemme/109428725810362095 kolektiva.social/@AvengingFemme: Response to Slaanesh re: "abuse apologist" posts and my position on eightpoint.app] (thread) ==History== Timestamps are according to archive.org, probably UTC. * '''2022.12.09''': moderator is no "12of47", a user who also had a [https://toot.cat/@12of47 TootCat account]. The following record is not intended as criticism of that user: ** '''.12.07 19:46''': [https://toot.cat/@12of47/109475290428576687 toot.cat/@12of47] {{fmt/quote|thinkin about moving to eightpoint as our primary server. Let´s see if we can}} ** '''.12.07 21:57''': [https://toot.cat/@12of47/109475806250322119 toot.cat/@12of47] {{fmt/quote|will be spending most of our time on 12@eightpoint.app now, go follow us there, cuties}} ** '''.12.09 09:46''': [https://toot.cat/@12of47/109484255733184547 toot.cat/@12of47] {{fmt/quote|every single person who worked to get http://eightpoint.app shut down, we curse you to never find a home, to always feel fucking isolated from every space you ever exist in, to never feel safe to be yourself, as you are doing to us}} ** '''.12.09 14:08''': [https://toot.cat/@12of47/109485286007607549 toot.cat/@12of47] (three similar posts later) {{fmt/quote|we are now the new owner of http://eightpoint.app! We are fucking Kallai, and we will never die to the actions of the fash}} ** 12of47 ([https://eightpoint.app/@12 eightpoint.app/@12]) remains admin of 8P as of 2022.12.20. (Whoever owns the domain and the server, of course, retains ultimate control, and we don't know who that is.) * '''2022.12.07''': moderator is now "@admin" ([[:File:2022-12-07.screen.eightpoint.png|screenshot]]) ** There is no evidence that this account remained beyond .12.08. (.12.07: [https://web.archive.org/web/20221207221550/https://eightpoint.app/@admin archive.org]; .12.08: [[:File:2022-12-08.screen.eightpoint.png|screenshot]]). [https://eightpoint.app/@admin Gone] as of .12.14. * '''2022.11.20''' - '''.12.04''': 8P comes back online ([[:File:2022-12-04.211747.screen.eightpoint.png|.12.04]]), apparently with a software upgrade ** the distinctive 8-point star logo is in the site header at [https://mew.toot.cat/wikiup/6/6b/2022-12-04.054229.screen.eightpoint.png 05:42:29] but has reverted to default Mastodon artwork by [[:File:2022-12-04.211747.screen.eightpoint.png|21:17:47]] ** moderator is now [https://eightpoint.app/@egirlterra Terra] - account exists from [https://web.archive.org/web/20221116115852/https://eightpoint.app/@egirlterra 11-16] to [https://web.archive.org/web/20221209163043/https://eightpoint.app/@egirlterra .12.09], gone as of .12.14 * '''2022.11.18''' - '''.11.20''': 8P goes offline sometime during this span ([[:File:2022-11-18.screen.eightpoint.png|.11.18]], [[:File:2022-11-20.screen.eightpoint.down.png|.11.20]]) * '''2022.11.12''' earliest online presence of 8P on archive.org ([[:File:2022-11-12-2253.screen.eightpoint.app.png|screenshot]]) * '''2022.10.28''' domain is first registered 7a1dbcbc18e73931722e0949c49484e8174dea83 687 686 2022-12-22T01:27:06Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:silenced]] * '''site''': {{ls/domain|eightpoint.app}} ==About== [[Eightpoint.app]] (8P) is a Mastodon instance that raised numerous alarm-flags for us almost immediately without crossing any obvious lines. I silenced them on [https://toot.cat/@woozle/109513962788427811 2022.12.14]. ==Discussion== * '''2022.12.13''' ** [https://newsie.social/@jessothomson/109508467120794305 newsie.social/@jessothomson] {{fmt/quote|If you want to see how the eightpoint hate machine works...}} ** [https://rage.love/@admin/109509798935516208 rage.love/@admin: Eightpoint.app defederation notice, abuse discussion]: [[Slaanesh]] and {{l/ip|Laurelai Bailey}} * '''2022.12.10''' [https://kolektiva.social/@moderation/109490898623030949 KOLEKTIVA.SOCIAL MOD TEAM'S STATEMENT ON RECENT EVENTS] re 8P * '''2022.11.29''' [https://kolektiva.social/@AvengingFemme/109428725810362095 kolektiva.social/@AvengingFemme: Response to Slaanesh re: "abuse apologist" posts and my position on eightpoint.app] (thread) ==History== Timestamps are according to archive.org, probably UTC. * '''2022.12.09''': moderator is no "12of47", a user who also had a [https://toot.cat/@12of47 TootCat account]. The following record is not intended as criticism of that user: ** '''.12.07 19:46''': [https://toot.cat/@12of47/109475290428576687 toot.cat/@12of47] {{fmt/quote|thinkin about moving to eightpoint as our primary server. Let´s see if we can}} ** '''.12.07 21:57''': [https://toot.cat/@12of47/109475806250322119 toot.cat/@12of47] {{fmt/quote|will be spending most of our time on 12@eightpoint.app now, go follow us there, cuties}} ** '''.12.09 09:46''': [https://toot.cat/@12of47/109484255733184547 toot.cat/@12of47] {{fmt/quote|every single person who worked to get http://eightpoint.app shut down, we curse you to never find a home, to always feel fucking isolated from every space you ever exist in, to never feel safe to be yourself, as you are doing to us}} ** '''.12.09 14:08''': [https://toot.cat/@12of47/109485286007607549 toot.cat/@12of47] (three similar posts later) {{fmt/quote|we are now the new owner of http://eightpoint.app! We are fucking Kallai, and we will never die to the actions of the fash}} ** 12of47 ([https://eightpoint.app/@12 eightpoint.app/@12]) remains admin of 8P as of 2022.12.20. (Whoever owns the domain and the server, of course, retains ultimate control, and we don't know who that is.) * '''2022.12.07''': moderator is now "@admin" ([[:File:2022-12-07.screen.eightpoint.png|screenshot]]) ** There is no evidence that this account remained beyond .12.08. (.12.07: [https://web.archive.org/web/20221207221550/https://eightpoint.app/@admin archive.org]; .12.08: [[:File:2022-12-08.screen.eightpoint.png|screenshot]]). [https://eightpoint.app/@admin Gone] as of .12.14. * '''2022.11.20''' - '''.12.04''': 8P comes back online ([[:File:2022-12-04.211747.screen.eightpoint.png|.12.04]]), apparently with a software upgrade ** the distinctive 8-point star logo is in the site header at [https://mew.toot.cat/wikiup/6/6b/2022-12-04.054229.screen.eightpoint.png 05:42:29] but has reverted to default Mastodon artwork by [[:File:2022-12-04.211747.screen.eightpoint.png|21:17:47]] ** moderator is now [https://eightpoint.app/@egirlterra Terra] - account exists from [https://web.archive.org/web/20221116115852/https://eightpoint.app/@egirlterra 11-16] to [https://web.archive.org/web/20221209163043/https://eightpoint.app/@egirlterra .12.09], gone as of .12.14 * '''2022.11.18''' - '''.11.20''': 8P goes offline sometime during this span ([[:File:2022-11-18.screen.eightpoint.png|.11.18]], [[:File:2022-11-20.screen.eightpoint.down.png|.11.20]]) * '''2022.11.12''' earliest online presence of 8P on archive.org ([[:File:2022-11-12-2253.screen.eightpoint.app.png|screenshot]]) * '''2022.10.28''' domain is first registered d3e250644683c21d11f782d3aa639d6f04076749 14 205 673 2022-12-14T22:51:04Z Woozle 1 Created page with "instances that have been '''silenced''' on TootCat" wikitext text/x-wiki instances that have been '''silenced''' on TootCat b00a9a12cdbbc03b83e7f90be88f90e83e2bdbd8 0 206 675 2022-12-20T17:14:02Z Woozle 1 Created page with "{{fmt/title|Commercial Activity & Self-Promotion}} <onlyinclude> Accounts that appear to be oriented towards promoting a business will be suspended without warning unless we h..." wikitext text/x-wiki {{fmt/title|Commercial Activity & Self-Promotion}} <onlyinclude> Accounts that appear to be oriented towards promoting a business will be suspended without warning unless we have previously granted permission. We do wish to support individuals and cooperatively-organized groups engaged in activities to support themselves and their communities, but we also want to understand your goals and methods &ndash; and we will want to have some pretty solid communication around that established first. We will not accept paid advertising. We are all part of the human community, and we reject the idea that possession of money entitles the holder to obligations by others. </onlyinclude> cd965122b73f193bccb4d707d334287755cfb539 677 675 2022-12-20T17:42:30Z Woozle 1 wikitext text/x-wiki {{fmt/title|Commercial Activity & Self-Promotion}} <onlyinclude> Accounts that exist primarily to promote for-profit<ref name=profit /> activity will be suspended without warning unless we have previously granted an exception. We do wish to support activities that support workers, creators, and communities. This includes but is not limited to: * independent artists/authors promoting or selling their own work, preferably through independent venues * co-operatively owned sales venues We will not accept paid advertising. As members of a global community of sapient and compassionate beings, we reject the idea that possession of capitalist power-tokens entitles the holder to compel others. </onlyinclude> ==Discussion== * '''2022-12-20''' [https://toot.cat/@woozle/109546094618870056 toot.cat/@woozle] {{fmt/quote|I need to update TC's policy-page to reflect this, but I draw a strong distinction between (a) an account which only exists to promote something, vs. (b) an account that interacts socially but also sometimes has things to promote.}} ==History== * '''2022-12-20''' revised to be more explicitly nurturing of independent creators ==Footnote== {{i/val|refs}} 730045d3b39424fa57dc87a936be9c9730a54532 679 677 2022-12-20T17:52:53Z Woozle 1 wikitext text/x-wiki {{fmt/title|Commercial Activity & Self-Promotion}} <onlyinclude> Accounts that exist primarily to promote for-profit<ref name=profit /> activity will be suspended without warning unless we have previously granted an exception. We do wish to support activities that support workers, creators, and communities. This includes but is not limited to: * independent artists/authors promoting or selling their own work or services, preferably through independent venues * individually or co-operatively-owned sales venues * individually or co-operatively-owned services We will not accept paid advertising. As members of a global community of sapient and compassionate beings, we reject the idea that possession of capitalist power-tokens entitles the holder to compel others. </onlyinclude> ==Discussion== * '''2022-12-20''' [https://toot.cat/@woozle/109546094618870056 toot.cat/@woozle] {{fmt/quote|I need to update TC's policy-page to reflect this, but I draw a strong distinction between (a) an account which only exists to promote something, vs. (b) an account that interacts socially but also sometimes has things to promote.}} ==History== * '''2022-12-20''' revised to be more explicitly nurturing of independent creators ==Footnote== {{i/val|refs}} ef4ca53551f88d0aeaa7516c6ed1efd28cca7022 0 207 676 2022-12-20T17:42:13Z Woozle 1 Created page with "<references> <ref name=profit>...in the sense of revenue that goes to owners solely for being owners, rather than as a means of helping to provide a living to workers/creators..." wikitext text/x-wiki <references> <ref name=profit>...in the sense of revenue that goes to owners solely for being owners, rather than as a means of helping to provide a living to workers/creators.</ref> </references> 2d3bc9462ee65de2a1fe1c378234dbf060a8e7d2 0 62 678 408 2022-12-20T17:51:22Z Woozle 1 wikitext text/x-wiki =Code of Conduct= ==General== As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users. We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination. Examples of unacceptable behavior include: <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Activity / Self-Promotion ('''[[/self-promo|&gt;&gt;]]''')== {{i/sub|self-promo}} ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> ==Footnotes== {{i/val|page={{PAGENAME}}/self-promo|refs}} b2ec9a1a5f25a0bf9e9b2a64470e4bc3fba39c4a 680 678 2022-12-20T18:03:37Z Woozle 1 wikitext text/x-wiki =Code of Conduct= ==Meta== This is not a contract. This is a guideline to help you understand how we, as a community, see and evaluate different kinds of behavior. We will always try to leave room for honest mistakes and misunderstandings, but we reserve the right to act without regard to strict or exacting interpretation of these guidelines. They are a statement of intention, and they are intended to reflect the views of the TootCat community. If you have comments or questions, please feel free to reach out to the TootCat Uberwensch ([https://toot.cat/@woozle @woozle]) whether or not you are a TootCat member. ^.^ ==General== As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users. We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination. Examples of unacceptable behavior include: <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>Users are empowered and responsible for addressing any abuses of the Code of Conduct such that the project remains an oppression-free experience.</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Activity / Self-Promotion ('''[[/self-promo|&gt;&gt;]]''')== {{i/sub|self-promo}} ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> ==Footnotes== {{i/val|page={{PAGENAME}}/self-promo|refs}} f23de38d1d7585452ab3018670a07e9c01d155dd 0 208 681 2022-12-20T19:19:27Z Woozle 1 Created page with "[[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although th..." wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) 26c466073e6f7d50a643ed5d65f390eeb0e21215 689 681 2022-12-22T14:28:25Z Woozle 1 wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in one context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable). ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. f9eb77cf2378664dee8d4ff860d2d5e9ca299a39 690 689 2022-12-22T14:29:30Z Woozle 1 /* Need Cases */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable). ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. 0bacf4fa49b7cd7ed5c917e0e1f415df5653fa39 691 690 2022-12-22T14:30:17Z Woozle 1 /* Need Cases */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. 3c003656e339001876d39283d1bc1b18c76b9353 692 691 2022-12-22T14:36:59Z Woozle 1 wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. 23bd3433d0cb9620484bc76bf3d5bac56beb6ec0 693 692 2022-12-22T15:58:43Z Woozle 1 wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. 88a8bd58f4877a49a65b3615f4ff6b986cf63280 694 693 2022-12-22T16:06:26Z Woozle 1 /* Discussion */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. f460cd6ebcf19ae47e84d0f386dfa50deda946b5 695 694 2022-12-22T16:07:51Z Woozle 1 /* Notes */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) a224863c5a3a28e7f2375e20ff73abe55426c1c0 707 695 2022-12-24T14:44:17Z Woozle 1 /* Discussion */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-23''' [https://wandering.shop/@Quinnae_Moon/109566758700954368 wandering.shop/@Quinnae_Moon] {{fmt/quote|It appears, at least in my little archipelago of Mastodons, that there's a Great Quote-Tweet debate happening.}} thread with discussion * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) f4cd82944ee6d7b6f8b2369ee8a2550cb126abb3 708 707 2022-12-24T15:36:05Z Woozle 1 /* Discussion */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-23''' [https://wandering.shop/@Quinnae_Moon/109566758700954368 wandering.shop/@Quinnae_Moon] {{fmt/quote|It appears, at least in my little archipelago of Mastodons, that there's a Great Quote-Tweet debate happening.}} thread with discussion * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-24''' [https://chat.noelle.codes/@noelle/109569025317272042 chat.noelle.codes/@noelle]: comment from an experienced Twitter ''and'' Mastodon user, and instance admin (she's been on fedi since at least 2017, just not on that instance) * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) 1d9ff1acef12959c71d6f97311436df5bb34f390 710 708 2022-12-24T19:56:52Z Woozle 1 /* Discussion */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-23''' [https://wandering.shop/@Quinnae_Moon/109566758700954368 wandering.shop/@Quinnae_Moon] {{fmt/quote|It appears, at least in my little archipelago of Mastodons, that there's a Great Quote-Tweet debate happening.}} thread with discussion * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-24''' [https://wandering.shop/@cstross/109570385865573556 Annalee Newitz via Charlie Stross] (If image OCR is available in Linux, I don't know how to do it. -W.) * '''2022-12-24''' [https://chat.noelle.codes/@noelle/109569025317272042 chat.noelle.codes/@noelle]: comment from an experienced Twitter ''and'' Mastodon user, and instance admin (she's been on fedi since at least 2017, just not on that instance) * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) e7a834fdc1b37ad46c625b09f5dd25103ba2a9f4 711 710 2022-12-24T22:18:08Z Woozle 1 /* neutral/discuss */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-24''' [https://wandering.shop/@annaleen/109570125073158983 Annalee Newitz] suggests a design feature that would alleviate their concerns (Annalee is generally against QTs) * '''2022-12-23''' [https://wandering.shop/@Quinnae_Moon/109566758700954368 wandering.shop/@Quinnae_Moon] {{fmt/quote|It appears, at least in my little archipelago of Mastodons, that there's a Great Quote-Tweet debate happening.}} thread with discussion * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-24''' [https://wandering.shop/@cstross/109570385865573556 Annalee Newitz via Charlie Stross] (If image OCR is available in Linux, I don't know how to do it. -W.) * '''2022-12-24''' [https://chat.noelle.codes/@noelle/109569025317272042 chat.noelle.codes/@noelle]: comment from an experienced Twitter ''and'' Mastodon user, and instance admin (she's been on fedi since at least 2017, just not on that instance) * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) 215eaa74fc2056059576d1a97041dfa17601a73b 0 1 682 615 2022-12-20T20:33:23Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''MeW''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about ** [[.cat]]: about the TLD ** [[Help:Contribute]]: how to help keep us running * '''Directories''': ** {{l/cat|Instance}}s *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe * ''''miscellaneous''': ** [[Quote toot]]: a much-requested but also much-loathed feature ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> 508d1dc2bb684131fc4b90c94d99b296e61c9368 685 682 2022-12-20T20:38:34Z Woozle 1 /* A Brief Directory */ wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''MeW''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about * '''[[TootCat]]''': ** [[Toot.cat/CoC|Code of Conduct]] ** [[Toot.cat/CoJ|Code of Justice]] ** [[Help:Contribute]]: how to help keep us running ** [[.cat]]: about the TLD * '''Directories''': ** {{l/cat|Instance}}s: *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe * '''miscellaneous''': ** [[Quote toot]]: a much-requested but also much-loathed feature ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> b94ba2b56232ace185a98ed590fd1045019466f1 0 89 683 605 2022-12-20T20:34:48Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2022-12-20''' Everything has been running more or less smoothly through the latest Twitter exodus deluges, as far as we can tell.}} d4fb7b6bd690f235cb3a7db70c24fd8e1caa6011 0 209 684 2022-12-20T20:36:38Z Woozle 1 Redirected page to [[Toot.cat]] wikitext text/x-wiki #redirect [[toot.cat]] 1e41cd07bd4cb15aa40a68f009538ad6e8c103c7 0 210 688 2022-12-22T01:42:29Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] [[category:co-op]] * '''site''': [https://social.coop/ home] [https://social.coop/about about] [https://social.coop/explore explore..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:co-op]] * '''site''': [https://social.coop/ home] [https://social.coop/about about] [https://social.coop/explore explore] ==About== [[social.coop]] (SC) is a Mastodon instance with a co-operative governance structure. ==Interesting Facts== * SC does not appear to have any relation to [[Social Coop]], itself somehow associated with [[Mask Network]] which acquired Japanese Mastodon instance [[pawoo.net]] on 2022-12-21 [https://markets.businessinsider.com/news/stocks/mask-network-acquires-pawoo-net-one-of-the-largest-mastodon-instances-1031984070?op=1][https://finance.yahoo.com/news/mask-network-acquires-pawoo-net-070000858.html] * SC's [https://wiki.social.coop/home.html wiki] is not actually a wiki but a site generated statically using [https://metalsmith.io/ Metalsmith]. * SC's domain was first registered on 2017-04-24. 4b6e0803721776aad547a9b3b4acf5d53bda71a9 697 688 2022-12-22T16:21:54Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:co-op]] * '''site''': [https://social.coop/ home] [https://social.coop/about about] [https://social.coop/explore explore] ==About== [[social.coop]] (SC) is a Mastodon instance with a co-operative governance structure. ==Interesting Facts== * SC does not appear to have any relation to [[Social Coop Limited]] (see [[pawoo.net]]). * SC's [https://wiki.social.coop/home.html wiki] is not actually a wiki but a site generated statically using [https://metalsmith.io/ Metalsmith]. * SC's domain was first registered on 2017-04-24. db77924b4eee452f755bc316b8c9c3ec40427c1e 0 211 696 2022-12-22T16:21:04Z Woozle 1 Created page with "[[category:instance]] [[category:mastodon]] [[category:Japan]] * '''site''': https://pawoo.net ==About== [[pawoo.net]] is a Japanese Mastodon instance with (as of 2022-12-22)..." wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:Japan]] * '''site''': https://pawoo.net ==About== [[pawoo.net]] is a Japanese Mastodon instance with (as of 2022-12-22) 797k users. It has been described as the second-largest Mastodon instance (after [[mastodon.social]], the "flagship" instance). ==News== * '''2022-12-21''' Pawoo has been acquired by [[Mask Network]] (which confusingly also owns or is related to an entity called [[Social Coop Limited]] that does not appear to have any relation to Mastodon instance [[social.coop]]). ** BI: [https://markets.businessinsider.com/news/stocks/mask-network-acquires-pawoo-net-one-of-the-largest-mastodon-instances-1031984070?op=1 Mask Network Acquires Pawoo.net, one of the largest Mastodon instances] ** Y!: [https://finance.yahoo.com/news/mask-network-acquires-pawoo-net-070000858.html Mask Network Acquires Pawoo.net, one of the largest Mastodon instances] bff9877a210bd8af13c42b4168234c24306ecfad 0 212 698 2022-12-24T13:20:24Z Woozle 1 Created page with "[[category:instance]] ==About== [[activitypub-proxy.cf]] is a site for circumventing fediblocks, using the [[lamp/activitypub-proxy]] open-source software written specifically..." wikitext text/x-wiki [[category:instance]] ==About== [[activitypub-proxy.cf]] is a site for circumventing fediblocks, using the [[lamp/activitypub-proxy]] open-source software written specifically for this purpose. a1a5c13376401838fcf5d24c422cedc22610727e 699 698 2022-12-24T13:21:13Z Woozle 1 wikitext text/x-wiki [[category:instance]] ==About== [[activitypub-proxy.cf]] is a site for circumventing fediblocks, using the [[activitypub-proxy]] open-source software written specifically for this purpose. 2c8e902179a54ed5ed79866aa9f179de53508a24 703 699 2022-12-24T13:31:36Z Woozle 1 wikitext text/x-wiki [[category:domain]] [[category:blocked]] ==About== [[activitypub-proxy.cf]] is a site for circumventing fediblocks, using the [[activitypub-proxy]] open-source software written specifically for this purpose. Actual connections are represented by subdomains: [[File:2022-12-24 at 08-28-34.screen.activitypub-proxy subdomains.png]] ("No limits imposed" is shown for each of these because we have blocked the base domain.) 6ff375eb02d7572c77a60d983a453feac77c014a 705 703 2022-12-24T13:53:46Z Woozle 1 wikitext text/x-wiki [[category:domain]] [[category:blocked]] ==About== [[activitypub-proxy.cf]] is a site for circumventing fediblocks, using the [[activitypub-proxy]] open-source software written specifically for this purpose. Actual connections are represented by subdomains: [[File:2022-12-24 at 08-28-34.screen.activitypub-proxy subdomains.png]] ("No limits imposed" is shown for each of these because we have blocked the base domain rather than trying to play whack-a-mole with subdomains.) 232036709664a94af2ab8048347c72585c0274bb 0 213 700 2022-12-24T13:27:14Z Woozle 1 Created page with "[[category:malware]] ==About== [[activitypub-proxy]] is open-source software written specifically for the purpose of circumventing fediblocks. According to [https://gitea.moe/..." wikitext text/x-wiki [[category:malware]] ==About== [[activitypub-proxy]] is open-source software written specifically for the purpose of circumventing fediblocks. According to [https://gitea.moe/lamp/activitypub-proxy the software's Git repository]: <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> This software is currently in use at [[activitypub-proxy.cf]]; we expect more such instances to pop up, given the apparent ease of installation. d03b436db11f50d959627d2b8459665d810f2186 701 700 2022-12-24T13:27:28Z Woozle 1 wikitext text/x-wiki [[category:malware]] ==About== [[activitypub-proxy]] is open-source software written specifically for the purpose of circumventing fediblocks. According to [https://gitea.moe/lamp/activitypub-proxy the software's Git repository]: <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> This software is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. e76c062192062255a8b4042c5d0255e0c6984bf4 704 701 2022-12-24T13:33:29Z Woozle 1 wikitext text/x-wiki [[category:malware]] ==About== [[activitypub-proxy]] is open-source software written specifically for the purpose of circumventing fediblocks. According to [https://gitea.moe/lamp/activitypub-proxy the software's Git repository] ([https://web.archive.org/web/20221223102518/https://gitea.moe/lamp/activitypub-proxy archive.org]): <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> This software is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. a9ec12e355981bc9f168f923c2710b15163fb9b6 706 704 2022-12-24T14:38:56Z Woozle 1 wikitext text/x-wiki [[category:malware]] ==About== [[activitypub-proxy]] is open-source software written specifically for the purpose of circumventing fediblocks. According to [https://gitea.moe/lamp/activitypub-proxy the software's Git repository] ([https://web.archive.org/web/20221223102518/https://gitea.moe/lamp/activitypub-proxy archive.org]): <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> This software is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. There is a tool for detecting usage of this malware [https://hachyderm.io/@tedivm/109569119442998113 in development as of 2022-12-24]. 9d14d156629fb4510bcce24702de49e3ec2dcf93 709 706 2022-12-24T19:33:55Z Woozle 1 wikitext text/x-wiki [[category:malware]] [[category:policy]] ==About== [[activitypub-proxy]] is open-source malware written specifically for the purpose of circumventing fediblocks (a consent violation). According to [https://gitea.moe/lamp/activitypub-proxy the software's Git repository] ([https://web.archive.org/web/20221223102518/https://gitea.moe/lamp/activitypub-proxy archive.org]): <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> This software is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. There is a tool for detecting usage of this malware [https://hachyderm.io/@tedivm/109569119442998113 in development as of 2022-12-24]. TootCat will fediblock any domain found to be hosting this software. aa1eafc5146b3b603fe4e2ef35aa0593e2b9dc11 712 709 2022-12-25T00:10:36Z Woozle 1 wikitext text/x-wiki [[category:malware]] [[category:policy]] ==About== [[activitypub-proxy]] (APP) is open-source malware written specifically for the purpose of circumventing fediblocks (a consent violation). According to [https://gitea.moe/lamp/activitypub-proxy APP's Git repository] as of 13:27 UTC and earlier ([https://web.archive.org/web/20221223102518/https://gitea.moe/lamp/activitypub-proxy archive.org]): <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> APP is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. There is a tool for detecting usage of this malware [https://hachyderm.io/@tedivm/109569119442998113 in development as of 2022-12-24]. TootCat will fediblock any domain found to be hosting this software. ==Arguments== ===APP revised self-justification=== APP's Git repository has been modified as of 2022-12-24 18:42 (ET) to include this argument in support of using it: <blockquote> The intended usage of this is as an alternative to using alt accounts or moving your account to circumvent whole-server blocks that have nothing to do with you and are unfairly cutting you off from mutuals, despite your particular account being compliant with their rules. </blockquote> The stated problem (whole-server blocks that are not the user's fault) is legit, but this is possibly the absolute worst way of dealing with it. * Most instances will only silence other instances known to not be festering cesspools, which allows users on the silencing instance to still follow individuals on the silenced instance. * If an instance has been blocked completely, it is probably a festering cesspool. If you are not yourself a supporter of festering cesspools, WTF are you still doing there? Go somewhere better. ** Sure, you're studying the cesspool like a scientist would study a contagious virus. Go for it. But science requires sacrifices, and federation with your cesspool-hosted account is one of them. * If you instance is not a festering cesspool and has been fully blocked for other reasons, consider asking your mutual to appeal to their instance admins to remove or soften the block. (TootCat has done this several times within recent memory.) * This tool does not ''merely'' allow innocent victims of misguided instance-blocking to evade domain-blocks, but also allows individuals who have been directly blocked -- either by an instance or by an individual -- to evade those blocks. Using it signals a willingness to evade other people's social boundaries, and is a bright red flag. ===admin-blocks violate consent?=== There have also been arguments made that administrative blocking (i.e. the entire instance doing a block, rather than individual users doing their own blocks) is somehow a violation of consent of the blocking instance's users. This argument is fash {{l/ip|bullshit}} that doesn't really deserve a response, but I will give one for the record. : '''1.''' On TootCat at least<ref name=others />, our users ''expect us to do this work'' and ''are grateful that they don't have to'' block every single troll themselves. We explain our blocking policy up front, and people join us with the expectation that we will actually ''act'' on it; failure to do so would be a violation of that trust, and of their consent. : '''2.''' Unless every user on an instance blocks a user, that user's posts will still show up in the federated timeline. Admin-blocking prevents that. Item 1 in particular shows how this argument is a reality-inversion, and therefore pure {{l/ip|concern trolling}}. ==Footnote== <references> <ref name=others>and, I would hope, most other instances -- with the obvious exception of "free speech" instances that basically don't believe in moderation and will do only that which is legally required</ref> </references> 5a7f5a820cdb60340053c9046f8c2edc50c65684 6 214 702 2022-12-24T13:30:18Z Woozle 1 [[category:screenshot]] {{c/date|2022-12-24}} wikitext text/x-wiki == Summary == [[category:screenshot]] {{c/date|2022-12-24}} 5355845f00bfab4f71dd584d8b0294f4142daf65 6 215 713 2022-12-25T00:24:56Z Woozle 1 [[category:screenshot]] {{c/date|2022-12-24}} * '''retrieved''' from [https://ryona.agency/objects/de9fd290-6050-4cb9-a6fd-d6e9431ea5ec ryona.agency] on 2022-12-24 wikitext text/x-wiki == Summary == [[category:screenshot]] {{c/date|2022-12-24}} * '''retrieved''' from [https://ryona.agency/objects/de9fd290-6050-4cb9-a6fd-d6e9431ea5ec ryona.agency] on 2022-12-24 980271e4755d65ffe1206c50d978efb50953a9be 714 713 2022-12-25T00:25:24Z Woozle 1 wikitext text/x-wiki == Summary == [[category:screenshot]] {{c/date|2022-12-24}} * '''retrieved''' from [https://ryona.agency/objects/de9fd290-6050-4cb9-a6fd-d6e9431ea5ec ryona.agency] (post was deleted less than an hour later) on 2022-12-24 0927db556696f9ba8fa60dd3bed7d97f10360e60 0 216 715 2022-12-25T00:27:49Z Woozle 1 Created page with "[[category:instance]] [[category:blocked]] * '''site''': https://ryona.agency/ ==About== [[ryona.agency]] initially came to our attention when their "Operator, CEO, inner pred..." wikitext text/x-wiki [[category:instance]] [[category:blocked]] * '''site''': https://ryona.agency/ ==About== [[ryona.agency]] initially came to our attention when their "Operator, CEO, inner predictor and [...] sole proprietor" [https://ryona.agency/mint @mint] defended [[activitypub-proxy]] while {{l/ip|tone policing}} a discussion of it: [[File:2022-12-24 at 19-21-28.mint@ryona.agency.png]] A quick investigation showed the following on @mint's profile ([https://archive.vn/BAg0H archive.is]): <blockquote> Not too fond of negroes, jews, women, hohols and transvestites. </blockquote> Whether this was sincere or just intended as a troll, it's the sort of toxic behavior we prefer not to invite to dinner. eed69c9c1b190b47f44093dabd901becc20a3343 6 217 716 2022-12-25T01:42:47Z Woozle 1 [[category:screenshot]] [[category:threat]] {{c/date|2022-12-24}} * '''retrieved''' on 2022-12-24 from [[cum.salon]] via [[toot.cat]]'s UI (the original had already been deleted) wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:threat]] {{c/date|2022-12-24}} * '''retrieved''' on 2022-12-24 from [[cum.salon]] via [[toot.cat]]'s UI (the original had already been deleted) 9e331ae5d677a4d72e57847e186b970106308461 0 218 717 2022-12-25T01:43:30Z Woozle 1 Created page with "[[category:Akkoma]] [[category:instance]] [[category:blocked]] [[category:child porn]] * '''site''': https://cum.salon ==About== [[cum.salon]] is an Akkoma instance which appe..." wikitext text/x-wiki [[category:Akkoma]] [[category:instance]] [[category:blocked]] [[category:child porn]] * '''site''': https://cum.salon ==About== [[cum.salon]] is an Akkoma instance which appears to be dominated by fash. As of 2022-12-24 ([https://archive.vn/yKjXg archive.is]), their site description says: <blockquote>Cum Salon is powered by Akkoma and ched, a webserver for child porn. Real raped women ages 06-17 at akko.disqordia.space</blockquote> (We also blocked [[disqordia.space]] some time ago.) I was originally just going to silence/mediablock them, but then a user threatened to slander me with an allegation of violent threats (see Fig. 1). af52b0fd7eebe0559ecd4d533f341c72185e1053 718 717 2022-12-25T01:46:32Z Woozle 1 wikitext text/x-wiki [[category:Akkoma]] [[category:instance]] [[category:blocked]] [[category:child porn]] [[File:2022-12-24 at 20-32-39.screen.thornernia.cum.salon.png|thumb|'''Fig. 1''': screenshot in TootCat's UI of a CS user claiming I had DMed one of their users a violent threat, complete with faked image of my supposed DM]] * '''site''': https://cum.salon ==About== [[cum.salon]] is an Akkoma instance which appears to be dominated by fash. As of 2022-12-24 ([https://archive.vn/yKjXg archive.is]), their site description says: <blockquote>Cum Salon is powered by Akkoma and ched, a webserver for child porn. Real raped women ages 06-17 at akko.disqordia.space</blockquote> (We also blocked [[disqordia.space]] some time ago.) I was originally just going to silence/mediablock them, but then [https://cum.salon/users/pernia one of their users] threatened to legally slander me with an allegation of violent threats (see Fig. 1). 4b4c3b76b4e45c5f97410eefb2d4c120116b762d 0 213 719 712 2022-12-25T13:34:03Z Woozle 1 /* admin-blocks violate consent? */ wikitext text/x-wiki [[category:malware]] [[category:policy]] ==About== [[activitypub-proxy]] (APP) is open-source malware written specifically for the purpose of circumventing fediblocks (a consent violation). According to [https://gitea.moe/lamp/activitypub-proxy APP's Git repository] as of 13:27 UTC and earlier ([https://web.archive.org/web/20221223102518/https://gitea.moe/lamp/activitypub-proxy archive.org]): <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> APP is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. There is a tool for detecting usage of this malware [https://hachyderm.io/@tedivm/109569119442998113 in development as of 2022-12-24]. TootCat will fediblock any domain found to be hosting this software. ==Arguments== ===APP revised self-justification=== APP's Git repository has been modified as of 2022-12-24 18:42 (ET) to include this argument in support of using it: <blockquote> The intended usage of this is as an alternative to using alt accounts or moving your account to circumvent whole-server blocks that have nothing to do with you and are unfairly cutting you off from mutuals, despite your particular account being compliant with their rules. </blockquote> The stated problem (whole-server blocks that are not the user's fault) is legit, but this is possibly the absolute worst way of dealing with it. * Most instances will only silence other instances known to not be festering cesspools, which allows users on the silencing instance to still follow individuals on the silenced instance. * If an instance has been blocked completely, it is probably a festering cesspool. If you are not yourself a supporter of festering cesspools, WTF are you still doing there? Go somewhere better. ** Sure, you're studying the cesspool like a scientist would study a contagious virus. Go for it. But science requires sacrifices, and federation with your cesspool-hosted account is one of them. * If you instance is not a festering cesspool and has been fully blocked for other reasons, consider asking your mutual to appeal to their instance admins to remove or soften the block. (TootCat has done this several times within recent memory.) * This tool does not ''merely'' allow innocent victims of misguided instance-blocking to evade domain-blocks, but also allows individuals who have been directly blocked -- either by an instance or by an individual -- to evade those blocks. Using it signals a willingness to evade other people's social boundaries, and is a bright red flag. ===admin-blocks violate consent?=== There have also been arguments made that administrative blocking (i.e. the entire instance doing a block, rather than individual users doing their own blocks) is somehow a violation of consent of the blocking instance's users. This argument is fash {{l/ip|bullshit}} that doesn't really deserve a response, but I will give one for the record. : '''1.''' On TootCat at least<ref name=others />, our users ''expect us to do this work'' and ''are grateful that they don't have to'' block every single troll themselves. We explain our blocking policy up front, and people join us with the expectation that we will actually ''act'' on it; failure to do so would be a violation of that trust, and of their consent. : '''2.''' Unless every user on an instance blocks a user, that user's posts will still show up in the federated timeline. Admin-blocking prevents that. Item 1 in particular shows how this argument is a reality-inversion (as well as {{l/wp|DARVO}}: the defederating admin is now the abuser, and the victims are the admin's own users and the troll), and therefore pure {{l/ip|concern trolling}}. ==Footnote== <references> <ref name=others>and, I would hope, most other instances -- with the obvious exception of "free speech" instances that basically don't believe in moderation and will do only that which is legally required</ref> </references> 5f35b0cc919914a50885af7001c3c9f41f8a2752 727 719 2022-12-28T12:48:39Z Woozle 1 wikitext text/x-wiki [[category:malware]] [[category:policy]] ==About== [[activitypub-proxy]] (APP) is open-source malware written specifically for the purpose of circumventing fediblocks (a consent violation). According to [https://gitea.moe/lamp/activitypub-proxy APP's Git repository] as of 13:27 UTC and earlier ([https://web.archive.org/web/20221223102518/https://gitea.moe/lamp/activitypub-proxy archive.org]): <blockquote> A simple proxy for ActivityPub that lets you circumvent blocks by masquerading as another domain name. [...] So for example, say you want to follow @kingu_platypus_gidora@octodon.social but the woke administrator has blocked you (or your instance blocked them wtf mastodon.social??), and you have a proxy at *.activitypub-proxy.cf: that would make @kingu_platypus_gidora@octodon-social.activitypub-proxy.cf which you can theoretically follow and fully interact with just like the real user. </blockquote> APP is currently in use at [[activitypub-proxy.cf]]; we expect more such relay domains to pop up, given the apparent ease of installation. There is a tool for detecting usage of this malware [https://hachyderm.io/@tedivm/109569119442998113 in development as of 2022-12-24]. TootCat will fediblock any domain found to be hosting this software. It was authored by fedi user "[[usr/lamp|lamp]]", a known bad actor. ==Arguments== ===APP revised self-justification=== APP's Git repository has been modified as of 2022-12-24 18:42 (ET) to include this argument in support of using it: <blockquote> The intended usage of this is as an alternative to using alt accounts or moving your account to circumvent whole-server blocks that have nothing to do with you and are unfairly cutting you off from mutuals, despite your particular account being compliant with their rules. </blockquote> The stated problem (whole-server blocks that are not the user's fault) is legit, but this is possibly the absolute worst way of dealing with it. * Most instances will only silence other instances known to not be festering cesspools, which allows users on the silencing instance to still follow individuals on the silenced instance. * If an instance has been blocked completely, it is probably a festering cesspool. If you are not yourself a supporter of festering cesspools, WTF are you still doing there? Go somewhere better. ** Sure, you're studying the cesspool like a scientist would study a contagious virus. Go for it. But science requires sacrifices, and federation with your cesspool-hosted account is one of them. * If you instance is not a festering cesspool and has been fully blocked for other reasons, consider asking your mutual to appeal to their instance admins to remove or soften the block. (TootCat has done this several times within recent memory.) * This tool does not ''merely'' allow innocent victims of misguided instance-blocking to evade domain-blocks, but also allows individuals who have been directly blocked -- either by an instance or by an individual -- to evade those blocks. Using it signals a willingness to evade other people's social boundaries, and is a bright red flag. ===admin-blocks violate consent?=== There have also been arguments made that administrative blocking (i.e. the entire instance doing a block, rather than individual users doing their own blocks) is somehow a violation of consent of the blocking instance's users. This argument is fash {{l/ip|bullshit}} that doesn't really deserve a response, but I will give one for the record. : '''1.''' On TootCat at least<ref name=others />, our users ''expect us to do this work'' and ''are grateful that they don't have to'' block every single troll themselves. We explain our blocking policy up front, and people join us with the expectation that we will actually ''act'' on it; failure to do so would be a violation of that trust, and of their consent. : '''2.''' Unless every user on an instance blocks a user, that user's posts will still show up in the federated timeline. Admin-blocking prevents that. Item 1 in particular shows how this argument is a reality-inversion (as well as {{l/wp|DARVO}}: the defederating admin is now the abuser, and the victims are the admin's own users and the troll), and therefore pure {{l/ip|concern trolling}}. ==Footnote== <references> <ref name=others>and, I would hope, most other instances -- with the obvious exception of "free speech" instances that basically don't believe in moderation and will do only that which is legally required</ref> </references> e49ffc7fdffc9c2888dcba732f57e1d6a5b14f1c 0 219 720 2022-12-25T14:40:55Z Woozle 1 Created page with "[[category:instance]] [[category:Misskey]] [[category:blocked]] * '''site''': https://fedi.intkos.link ==About== [[fedi.intkos.link]] is a [[Misskey]] instance that appears to..." wikitext text/x-wiki [[category:instance]] [[category:Misskey]] [[category:blocked]] * '''site''': https://fedi.intkos.link ==About== [[fedi.intkos.link]] is a [[Misskey]] instance that appears to federate with a lot of known troll and "free speech" sites. TootCat blocked them on 2022-12-25 for that reason. 14ab85953bd2825b05ea6ec9d65c89a0d41916a9 721 720 2022-12-25T14:50:15Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Misskey]] [[category:blocked]] * '''site''': https://fedi.intkos.link ==About== [[fedi.intkos.link]] (IL) is a [[Misskey]] instance that appears to federate with a lot of known troll and "free speech" sites. TootCat blocked them on 2022-12-25 for that reason, as well as trolling by IL user [https://fedi.intkos.link/@kino @kino]. ae8073fb0867dc41a06e209ca5aaa0797b5c80e0 723 721 2022-12-25T15:54:57Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Misskey]] [[category:blocked]] * '''site''': https://fedi.intkos.link ==About== [[fedi.intkos.link]] (IL) is a [[Misskey]] instance that appears to federate with a lot of known troll and "free speech" sites. TootCat blocked them on 2022-12-25 for that reason, as well as trolling by IL user [https://fedi.intkos.link/@kino @kino]. ==Notes== For reference: [https://toot.cat/@woozle/109571843437634629] [https://toot.cat/@woozle/109571628764583319] [https://toot.cat/@woozle/109571611583735520] [https://toot.cat/@woozle/109571563625162570] 47fdd47e16a2545f1067321e1598609da92fd635 0 220 722 2022-12-25T15:51:54Z Woozle 1 Created page with "[[category:instance]] [[category:Pleroma]] [[category:blocked]] * '''site''': https://fedi.pawlicker.com ==About== [[fedi.pawlicker.com]] is a [[Pleroma]] instance. TootCat bl..." wikitext text/x-wiki [[category:instance]] [[category:Pleroma]] [[category:blocked]] * '''site''': https://fedi.pawlicker.com ==About== [[fedi.pawlicker.com]] is a [[Pleroma]] instance. TootCat blocked them on 2022-12-24 due to trolling activity spearheaded by [https://fedi.pawlicker.com/users/PhenomX6 @PhenomX6]. I didn't get the sense that the instance would be willing to take action against that user. ==Notes== For reference: [https://toot.cat/@woozle/109571827271951813] [https://toot.cat/@woozle/109571705795355596] [https://toot.cat/@woozle/109571675039586860] (my posts, because theirs are no longer available). fc9364846ceacfcbd1063fe9584a58903b8b9ba6 0 208 724 711 2022-12-27T13:34:17Z Woozle 1 /* neutral/discuss */ wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot, most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-27''' [https://toot.cat/@thatdawnperson/109585785337817705 toot.cat/@thatdawnperson] {{fmt/quote|It is important that QT protect the original writer’s distribution/privacy settings. What does QT safely give you that reply-and-boost or sharing a link doesn’t? [...]}} To my mind, this suggests one ''benefit'' of QT-as-a-feature over manually constructing them: they could encourage best practices, such as making sure QTs were replies rather than new threads, or not QTing if the quoted user has disabled them on a given post (or as a default for their account). * '''2022-12-24''' [https://wandering.shop/@annaleen/109570125073158983 Annalee Newitz] suggests a design feature that would alleviate their concerns (Annalee is generally against QTs) * '''2022-12-23''' [https://wandering.shop/@Quinnae_Moon/109566758700954368 wandering.shop/@Quinnae_Moon] {{fmt/quote|It appears, at least in my little archipelago of Mastodons, that there's a Great Quote-Tweet debate happening.}} thread with discussion * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-24''' [https://wandering.shop/@cstross/109570385865573556 Annalee Newitz via Charlie Stross] (If image OCR is available in Linux, I don't know how to do it. -W.) * '''2022-12-24''' [https://chat.noelle.codes/@noelle/109569025317272042 chat.noelle.codes/@noelle]: comment from an experienced Twitter ''and'' Mastodon user, and instance admin (she's been on fedi since at least 2017, just not on that instance) * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) 95b3d1ca34125823ce1ce16ef2a3fddfaa4703ec 6 221 725 2022-12-28T12:41:37Z Woozle 1 [[category:screenshot]] {{c/date|2022-12-24}} * '''retrieved''' 2022-12-24 (screenshot taken the next day, by which time the actual discussion had disappeared but I still had it open in a tab) wikitext text/x-wiki == Summary == [[category:screenshot]] {{c/date|2022-12-24}} * '''retrieved''' 2022-12-24 (screenshot taken the next day, by which time the actual discussion had disappeared but I still had it open in a tab) 13a8d02578b7c375fac14eee9f33ab9971bba146 0 222 726 2022-12-28T12:47:17Z Woozle 1 Created page with "[[category:fedi user|lamp]] ==About== '''lamp''' is a known bad actor on the fediverse, worst known for creating the [[Activitypub-proxy]] open-source malware. ==Links== ===Of..." wikitext text/x-wiki [[category:fedi user|lamp]] ==About== '''lamp''' is a known bad actor on the fediverse, worst known for creating the [[Activitypub-proxy]] open-source malware. ==Links== ===Official=== * [https://owo69.me/ home site] * [https://gitea.moe Gitea instance] ** [https://gitea.moe/lamp/lamp/src/branch/master/list%20of%20my%20domains%20.md list of domains] ([https://web.archive.org/web/20220924151724/https://gitea.moe/lamp/lamp/src/branch/master/list%20of%20my%20domains%20.md archive.org]) 5e692226f244ea8d81b535061187592499ec293b 733 726 2023-01-01T14:55:44Z Woozle 1 wikitext text/x-wiki [[category:fedi user|lamp]] ==About== '''lamp''' is a known sometimes-bad actor on the fediverse, worst known for creating the [[Activitypub-proxy]] open-source malware. ==Links== ===Official=== * [https://owo69.me/ home site] * [https://gitea.moe Gitea instance] ** [https://gitea.moe/lamp/lamp/src/branch/master/list%20of%20my%20domains%20.md list of domains] ([https://web.archive.org/web/20220924151724/https://gitea.moe/lamp/lamp/src/branch/master/list%20of%20my%20domains%20.md archive.org]) * Fedi account: ** [https://boobytooth.social/@lamp boobytooth.social/@lamp] 8a38a7b6237231a8052ab08cdb2865a7ee4d0efe 0 223 728 2022-12-29T13:31:18Z Woozle 1 Created page with "[[category:domain]] [[category:pseudo-instance]] * '''site''': https://mastinator.com/ ==About== [[mastinator.com]] is a [[pseudo-instance]] which provides "disposable public..." wikitext text/x-wiki [[category:domain]] [[category:pseudo-instance]] * '''site''': https://mastinator.com/ ==About== [[mastinator.com]] is a [[pseudo-instance]] which provides "disposable public anonymous no-login Fediverse accounts". While there may be legitimate uses for such a tool, we are not presently aware of any -- and the most likely primary design-case would seem to be block-evasion, which is not okay. At least two users reported them to me on the morning of 2022-12-29, and I immediately blocked them. -W. faa0eaf60eeccfd45cd5ee0331ce6ffdb1ba7ab0 0 212 729 705 2022-12-29T13:42:47Z Woozle 1 wikitext text/x-wiki [[category:domain]] [[category:pseudo-instance]] [[category:blocked]] ==About== [[activitypub-proxy.cf]] is a site for circumventing fediblocks, using the [[activitypub-proxy]] open-source software written specifically for this purpose. Actual connections are represented by subdomains: [[File:2022-12-24 at 08-28-34.screen.activitypub-proxy subdomains.png]] ("No limits imposed" is shown for each of these because we have blocked the base domain rather than trying to play whack-a-mole with subdomains.) 157873178f547d95d4ac4d1b7a4a36a1bda0092f 14 224 730 2022-12-29T13:43:39Z Woozle 1 Created page with "pages about internet domains" wikitext text/x-wiki pages about internet domains ed2a51070da69f76408e844c4ccc81f2ada519f1 14 36 731 425 2022-12-29T13:46:18Z Woozle 1 wikitext text/x-wiki [[category:domain]] instances on the Mastodon fediverse The way ActivityPub is set up (which is true for most/all federated protocols), every instance is also a {{lc|domain}}. 45e5e96cffce5c95850eb36a7153faec15599c28 0 225 732 2022-12-30T16:34:26Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] * '''site''': https://c.im/about ==Discussion== * '''2022-12-30''' [https://oliphant.social/@Blackfist/109597851412606231 oliphant...." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': https://c.im/about ==Discussion== * '''2022-12-30''' [https://oliphant.social/@Blackfist/109597851412606231 oliphant.social/@Blackfist] apparently got banned for merely ''alluding'' to racism. It seems likely they are using the racist definition of "racism", i.e. the opposite of what it actually means. be7b80f12b00b522df7fd5d4634b1a1758e7158c 0 216 734 715 2023-01-02T16:03:21Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:blocked]] * '''site''': https://ryona.agency/ ==About== [[ryona.agency]] initially came to our attention when their "Operator, CEO, inner predictor and [...] sole proprietor" [https://ryona.agency/mint @mint] defended [[activitypub-proxy]] while {{l/ip|tone policing}} a discussion of it: [[File:2022-12-24 at 19-21-28.mint@ryona.agency.png]] A quick investigation showed the following on @mint's profile ([https://archive.vn/BAg0H archive.is]): <blockquote> Not too fond of negroes, jews, women, hohols and transvestites. </blockquote> Whether this was sincere or just intended as a troll, it's the sort of toxic behavior we prefer not to invite to dinner. ==Records== * [[:File:2022-12-25 at 13-03-28.screen.(@mint@ryona.agency).png|2022-12-25 dialogue screenshot]] 6ca5b9c5bf3a852bee8d9c465d2adace15855027 0 226 735 2023-01-02T16:29:48Z Woozle 1 Created page with "[[category:instance]] '''site''': [https://inktos.link TLD], [https://fedi.inktos.link instance]: note no response from either on 2023-01-02 ==Records== * :File:2022-12-25 a..." wikitext text/x-wiki [[category:instance]] '''site''': [https://inktos.link TLD], [https://fedi.inktos.link instance]: note no response from either on 2023-01-02 ==Records== * [[:File:2022-12-25 at 13-03-28.screen.(@mint@ryona.agency).png|2022-12-25 dialogue screenshot]] f197e7cf88b67ab96105bb78555d76b204f24c58 0 227 736 2023-01-02T16:33:51Z Woozle 1 Created page with "[[category:instance]] [[category:akkoma]] '''site''': [https://kyaruc.moe Grafana], [https://ak.kyaruc.moe Akkoma] ==About== '''ak.kyaruc.moe''' is a problematic single user i..." wikitext text/x-wiki [[category:instance]] [[category:akkoma]] '''site''': [https://kyaruc.moe Grafana], [https://ak.kyaruc.moe Akkoma] ==About== '''ak.kyaruc.moe''' is a problematic single user instance. ==Records== * [[:File:2022-12-25 at 13-03-28.screen.(@mint@ryona.agency).png|2022-12-25 dialogue screenshot]] 46c42813cc9048bf01f62503e53071b9dde08149 0 228 737 2023-01-03T15:45:14Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] * '''site''': https://bylines.social/ ** '''main/admin''': [https://bylines.social/@clarion @clarion] ==About== [[bylines.social]]..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': https://bylines.social/ ** '''main/admin''': [https://bylines.social/@clarion @clarion] ==About== [[bylines.social]] is a Mastodon instance created by/for the [https://bylinesnetwork.co.uk/ Bylines Network], with Yorkshire Bylines as the primary poster currently. ==Report== A user reported [https://bylines.social/@YorksBylines/109619544194168335 this post], concerned that it represented an invitation to (re)open "debate" on whether trans people are who they say they are: * '''2023-01-02''' [https://bylines.social/@YorksBylines/109619544194168335 bylines.social/@YorksBylines] {{fmt/quote|If we can establish a consensus that trans men are men and trans women are women, it is likely to add to the safety of all as it increases the open-mindedness of society and challenges fears and divisions | Andy Brown / #Bylines #Transgender #TransRightsAreHumanRights}} ** linked: '''2023-01-02''' [https://yorkshirebylines.co.uk/politics/transgender-rights-everything-old-is-new-again/ Transgender rights: everything old is new again] {{fmt/quote|Whenever any section of society starts to stand up for its rights it faces a barrage of criticism and people come up with some very overblown theories about what will go wrong if we start treating them more reasonably.}} It's entirely understandable to be concerned about any framing of trans rights as a "debate", but I think this post is more about seeking to establish a solid consensus ''against'' the the idea that such debate is legitimate -- where the purpose of "consensus" in this context is that nobody can get away with pretending there's any serious debate on the matter. Looking at a smattering of other posts on the instance and on the Yorkshire Bylines site, they seem solidly reality-based. 166937e437ee3aa15c8f1f86a558b913cc4de02f 738 737 2023-01-04T20:55:14Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': https://bylines.social/ ** '''main/admin''': [https://bylines.social/@clarion @clarion] ==About== [[bylines.social]] is a Mastodon instance created by/for the [https://bylinesnetwork.co.uk/ Bylines Network], with Yorkshire Bylines as the primary poster currently. While they appear to be firmly reality-based, they also appear to have had rather poor judgement regarding moderation. ==Report== A user reported [https://bylines.social/@YorksBylines/109619544194168335 this post], concerned that it represented an invitation to (re)open "debate" on whether trans people are who they say they are: * '''2023-01-02''' [https://bylines.social/@YorksBylines/109619544194168335 bylines.social/@YorksBylines] {{fmt/quote|If we can establish a consensus that trans men are men and trans women are women, it is likely to add to the safety of all as it increases the open-mindedness of society and challenges fears and divisions | Andy Brown / #Bylines #Transgender #TransRightsAreHumanRights}} ** linked: '''2023-01-02''' [https://yorkshirebylines.co.uk/politics/transgender-rights-everything-old-is-new-again/ Transgender rights: everything old is new again] {{fmt/quote|Whenever any section of society starts to stand up for its rights it faces a barrage of criticism and people come up with some very overblown theories about what will go wrong if we start treating them more reasonably.}} It's entirely understandable to be concerned about any framing of trans rights as a "debate", but I think this post is more about seeking to establish a solid consensus ''against'' the the idea that such debate is legitimate -- where the purpose of "consensus" in this context is that nobody can get away with pretending there's any serious debate on the matter. Looking at a smattering of other posts on the instance and on the Yorkshire Bylines site, they seem solidly reality-based. ==Commentary== * '''2023-01-03''' [https://freethoughtblogs.com/pharyngula/2023/01/03/effective-shunning/ Effective shunning] ([https://octodon.social/@pzmyers/109625736155255416 via]) {{fmt/quote|One of the bonuses of being on Mastodon is the fediverse is actually strong about crushing bad actors. A shiny new newspaper out of Yorkshire trying to make it in an online world published a lazy, stupid opinion piece about trans people — it’s England, you know, the place is infested with transphobes — and got [https://masto.ai/@stavvers/109625132804829976 slammed hard for it].}} ** Note: I have not been able to find the opinion piece described. -W. 834c165bdb475f5d839d5cc758b74db447b40f7d 756 738 2023-01-17T19:25:03Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': https://bylines.social/ ** '''main/admin''': [https://bylines.social/@clarion @clarion] ==About== [[bylines.social]] is a Mastodon instance created by/for the [https://bylinesnetwork.co.uk/ Bylines Network], with Yorkshire Bylines as the primary poster currently. While they appear to be firmly reality-based, they also appear to have had rather poor judgement regarding moderation. ==History== * '''2023-01-17''' [https://toot.cat/@news/109706098784877596 blocked for transmisia] -- I guess they were still being too light in moderating the fash. {{w/init}} * '''2023-01-03''' [https://freethoughtblogs.com/pharyngula/2023/01/03/effective-shunning/ Effective shunning] ([https://octodon.social/@pzmyers/109625736155255416 via]) {{fmt/quote|One of the bonuses of being on Mastodon is the fediverse is actually strong about crushing bad actors. A shiny new newspaper out of Yorkshire trying to make it in an online world published a lazy, stupid opinion piece about trans people — it’s England, you know, the place is infested with transphobes — and got [https://masto.ai/@stavvers/109625132804829976 slammed hard for it].}} ** Note: I have not been able to find the opinion piece described. {{w/init}} * '''2023-01-02''' [https://bylines.social/@YorksBylines/109619544194168335 bylines.social/@YorksBylines] {{fmt/quote|If we can establish a consensus that trans men are men and trans women are women, it is likely to add to the safety of all as it increases the open-mindedness of society and challenges fears and divisions | Andy Brown / #Bylines #Transgender #TransRightsAreHumanRights}} ** linked: '''2023-01-02''' [https://yorkshirebylines.co.uk/politics/transgender-rights-everything-old-is-new-again/ Transgender rights: everything old is new again] {{fmt/quote|Whenever any section of society starts to stand up for its rights it faces a barrage of criticism and people come up with some very overblown theories about what will go wrong if we start treating them more reasonably.}} ** A user reported [https://bylines.social/@YorksBylines/109619544194168335 this post], concerned that it represented an invitation to (re)open "debate" on whether trans people are who they say they are: *** It's entirely understandable to be concerned about any framing of trans rights as a "debate", but I think this post is more about seeking to establish a solid consensus ''against'' the the idea that such debate is legitimate -- where the purpose of "consensus" in this context is that nobody can get away with pretending there's any serious debate on the matter. Looking at a smattering of other posts on the instance and on the Yorkshire Bylines site, they seem solidly reality-based. {{w/init}} a9cbdff4fcc0e6691037330de373c23ad116492d 757 756 2023-01-17T19:25:54Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:blocked]] [[category:transmisia]] * '''site''': https://bylines.social/ ** '''main/admin''': [https://bylines.social/@clarion @clarion] ==About== [[bylines.social]] is a Mastodon instance created by/for the [https://bylinesnetwork.co.uk/ Bylines Network], with Yorkshire Bylines as the primary poster currently. While they appear to be firmly reality-based, they also appear to have had rather poor judgement regarding moderation. ==History== * '''2023-01-17''' [https://toot.cat/@news/109706098784877596 blocked for transmisia] -- I guess they were still being too light in moderating the fash. {{w/init}} * '''2023-01-03''' [https://freethoughtblogs.com/pharyngula/2023/01/03/effective-shunning/ Effective shunning] ([https://octodon.social/@pzmyers/109625736155255416 via]) {{fmt/quote|One of the bonuses of being on Mastodon is the fediverse is actually strong about crushing bad actors. A shiny new newspaper out of Yorkshire trying to make it in an online world published a lazy, stupid opinion piece about trans people — it’s England, you know, the place is infested with transphobes — and got [https://masto.ai/@stavvers/109625132804829976 slammed hard for it].}} ** Note: I have not been able to find the opinion piece described. {{w/init}} * '''2023-01-02''' [https://bylines.social/@YorksBylines/109619544194168335 bylines.social/@YorksBylines] {{fmt/quote|If we can establish a consensus that trans men are men and trans women are women, it is likely to add to the safety of all as it increases the open-mindedness of society and challenges fears and divisions | Andy Brown / #Bylines #Transgender #TransRightsAreHumanRights}} ** linked: '''2023-01-02''' [https://yorkshirebylines.co.uk/politics/transgender-rights-everything-old-is-new-again/ Transgender rights: everything old is new again] {{fmt/quote|Whenever any section of society starts to stand up for its rights it faces a barrage of criticism and people come up with some very overblown theories about what will go wrong if we start treating them more reasonably.}} ** A user reported [https://bylines.social/@YorksBylines/109619544194168335 this post], concerned that it represented an invitation to (re)open "debate" on whether trans people are who they say they are: *** It's entirely understandable to be concerned about any framing of trans rights as a "debate", but I think this post is more about seeking to establish a solid consensus ''against'' the the idea that such debate is legitimate -- where the purpose of "consensus" in this context is that nobody can get away with pretending there's any serious debate on the matter. Looking at a smattering of other posts on the instance and on the Yorkshire Bylines site, they seem solidly reality-based. {{w/init}} 5a1b1a2f6f699ad6ac6fcc29374323a1bff8896f 14 229 739 2023-01-05T01:47:20Z Woozle 1 Created page with "instances that have been blocked There is often related discussion on the [https://toot.cat/tags/fediblock #fediblock] tag." wikitext text/x-wiki instances that have been blocked There is often related discussion on the [https://toot.cat/tags/fediblock #fediblock] tag. 4cffecb37bb4ad006f3f0053acd7bb5fd412390d 0 230 740 2023-01-13T00:38:48Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] '''site''': {{ls/domain|blacksun.social}} ==About== Despite the domain name's allusion to {{l/wp|Black Sun (symbol)|neo-Nazi symbol..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] '''site''': {{ls/domain|blacksun.social}} ==About== Despite the domain name's allusion to {{l/wp|Black Sun (symbol)|neo-Nazi symbology}}, this instance appears to be genuinely anti-Nazi, egalitarian, and epistemically positive. Their self-description as of 2022-01-12: <blockquote>Anti-fascist. Science and Federation values. Liberal social-democratic activism. LGBTQ+ friendly and woke af. Institutionalist utilitarianism. Radically secular. Free of glurge and disinformation.</blockquote> 247666f882301d075488df1f978f15e2d814fdb5 6 231 741 2023-01-17T00:42:51Z Woozle 1 [[category:screenshot]] [[category:moth.zone]] '''retrieved''' from [https://rage.love/system/media_attachments/files/108/806/507/059/184/814/original/ef34591ce7c52a72.png rage.love] via [https://rage.love/@puf/108806514088155480 rage.love/@puf] on 2023-01-16 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:moth.zone]] '''retrieved''' from [https://rage.love/system/media_attachments/files/108/806/507/059/184/814/original/ef34591ce7c52a72.png rage.love] via [https://rage.love/@puf/108806514088155480 rage.love/@puf] on 2023-01-16 d2649a6a136225102f144b69a87c4968951e2206 742 741 2023-01-17T00:47:50Z Woozle 1 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:moth.zone]] * '''retrieved''' from [https://rage.love/system/media_attachments/files/108/806/507/059/184/814/original/ef34591ce7c52a72.png rage.love] via [https://rage.love/@puf/108806514088155480 rage.love/@puf] on 2023-01-16 ** The original post is, unfortunately, no longer available directly or in any known archive. It was apparently deleted within 2 days of this screenshot. 3b87450bb7fdf8b03b4b0f326d34ddf55e4ba651 0 232 743 2023-01-17T00:52:26Z Woozle 1 Created page with "[[category:instance]] '''site''': {{ls/domain|akko.moth.zone}} [[File:Ef34591ce7c52a72.png|thumb|'''Fig. 1''': root@moth.zone says to @eris (of [[Disqordia]]) {{fmt/quote|damn..." wikitext text/x-wiki [[category:instance]] '''site''': {{ls/domain|akko.moth.zone}} [[File:Ef34591ce7c52a72.png|thumb|'''Fig. 1''': root@moth.zone says to @eris (of [[Disqordia]]) {{fmt/quote|damn, they [ubuntu.buzz] haven't blocked me either huh / i guess I'm not white enough}}]] ==About== [[moth.zone]] is an ActivityPub instance. They appear to be friendly to low-key racism of the "reverse discrimination" ilk, in that their apparent admin (root@moth.zone) implied that another instance, [[ubuntu.buzz]], was blocking anyone simply for being too white (rather than, as seems more likely, for being racist) -- see Figure 1. Additional confidential reporting suggests that this is part of a consistent pattern of behavior -- generally conversing casually with racists and mocking any Black-run instances that don't block them. ==History== * '''2023-01-16''' TootCat blocks moth.zone 5ce0ecb78567952f707051c683e521e9d71b86b9 745 743 2023-01-17T01:00:01Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:blocked]] '''site''': {{ls/domain|akko.moth.zone}} [[File:Ef34591ce7c52a72.png|thumb|'''Fig. 1''': root@moth.zone says to @eris (of [[Disqordia]]) {{fmt/quote|damn, they [ubuntu.buzz] haven't blocked me either huh / i guess I'm not white enough}}]] ==About== [[moth.zone]] is an ActivityPub instance. They appear to be friendly to low-key racism of the "reverse discrimination" ilk, in that their apparent admin (root@moth.zone) implied that another instance, [[ubuntu.buzz]], was blocking anyone simply for being too white (rather than, as seems more likely, for being racist) -- see Figure 1. Additional confidential reporting suggests that this is part of a consistent pattern of behavior -- generally conversing casually with racists and mocking any Black-run instances that don't block them. ==History== * '''2023-01-16''' TootCat blocks moth.zone bad1c997ee3c170d6b05a73a557d4ef15e8d226a 753 745 2023-01-17T01:48:42Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:blocked]] [[category:racism]] '''site''': {{ls/domain|akko.moth.zone}} [[File:Ef34591ce7c52a72.png|thumb|'''Fig. 1''': root@moth.zone says to @eris (of [[Disqordia]]) {{fmt/quote|damn, they [ubuntu.buzz] haven't blocked me either huh / i guess I'm not white enough}}]] ==About== [[moth.zone]] is an ActivityPub instance. They appear to be friendly to low-key racism of the "reverse discrimination" ilk, in that their apparent admin (root@moth.zone) implied that another instance, [[ubuntu.buzz]], was blocking anyone simply for being too white (rather than, as seems more likely, for being racist) -- see Figure 1. Additional confidential reporting suggests that this is part of a consistent pattern of behavior -- generally conversing casually with racists and mocking any Black-run instances that don't block them. ==History== * '''2023-01-16''' TootCat blocks moth.zone * '''2022-09-13''' [https://weirder.earth/@packbat/108992791415798214 weirder.earth/@packbat] contextualizes the series of events around a #fediblock recommendation for moth.zone in various ways. It also explains why [[ubuntu.buzz]] shut down (Black instance, received harassment). e98fe33a5e8d1fe97fd80828314a044b96d66c4a 0 233 744 2023-01-17T00:59:29Z Woozle 1 Created page with "[[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== disqor..." wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them some time before this writing, probably late 2022. ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] 3ccc54b0cfe75ab97a5da8576316746f2ce80367 747 744 2023-01-17T01:02:22Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment some time before this writing, probably late 2022. ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] 80870d6ba4dc7190cc6176bc0eb3b9d9d3c6ff32 748 747 2023-01-17T01:07:16Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] 54da642802c9cf23042f2bf069930bc297e66725 749 748 2023-01-17T01:17:25Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space * '''2022-08-13''' [https://weirder.earth/@packbat/108815931937152540 weirder.earth/@packbat] ([https://web.archive.org/web/20221219143455/https://weirder.earth/@packbat/108815931937152540 archive.org]) critiques Disqordia's behavior ** Much of the Disqordia thread xey refer to is still available in [https://web.archive.org/web/20220816090453/https://akko.disqordia.space/notice/AMOna3GxzSqiJN6t9M archive.org]. ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] 58e196a45cf32b6ec945ce9f8a3ee50c7db85bbe 750 749 2023-01-17T01:31:34Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space * '''2022-08-13''' [https://weirder.earth/@packbat/108815931937152540 weirder.earth/@packbat] ([https://web.archive.org/web/20221219143455/https://weirder.earth/@packbat/108815931937152540 archive.org]) critiques Disqordia's behavior ** Much of the Disqordia thread xey refer to is still available in [https://web.archive.org/web/20220816090453/https://akko.disqordia.space/notice/AMOna3GxzSqiJN6t9M archive.org]. * '''2022-07-04''' [https://jubi.life/@sixthhokage95/108592329213498710 jubi.life/@sixthhokage95] ([https://web.archive.org/web/20220816050124/https://cybre.space/@DangerDyke/108595663835969647 archive.org]): thread in which [https://disqordia.space/users/eris disqordia.space/users/eris] is clearly being deliberately (but subtly) provocative in a racist way; [https://cybre.space/@DangerDyke/ cybre.space/@DangerDyke] then defends eris ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] dafbbc0bc0fad34b6315aa9d3db7b5fabf3ec537 751 750 2023-01-17T01:40:10Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space * '''2022-08-13''' [https://weirder.earth/@packbat/108815931937152540 weirder.earth/@packbat] ([https://web.archive.org/web/20221219143455/https://weirder.earth/@packbat/108815931937152540 archive.org]) critiques Disqordia's behavior ** Much of the Disqordia thread xey refer to is still available in [https://web.archive.org/web/20220816090453/https://akko.disqordia.space/notice/AMOna3GxzSqiJN6t9M archive.org]. * '''2022-07-04''' [https://jubi.life/@sixthhokage95/108592329213498710 jubi.life/@sixthhokage95] ([https://web.archive.org/web/20220816050124/https://cybre.space/@DangerDyke/108595663835969647 archive.org]): thread in which [https://disqordia.space/users/eris disqordia.space/users/eris] is clearly being deliberately (but subtly) provocative in a racist way; [https://cybre.space/@DangerDyke/ cybre.space/@DangerDyke] then defends eris ** [https://rage.love/@puf/108829477530153878 rage.love/@puf] ([https://web.archive.org/web/20221219225856/https://rage.love/@puf/108829477530153878 archive.org]) provides screenshots of that and additional bad behavior from eris ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] 551e19c99dff50c13d975152a1110272b28faf20 752 751 2023-01-17T01:46:04Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] [[category:racism]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space * '''2022-08-13''' [https://weirder.earth/@packbat/108815931937152540 weirder.earth/@packbat] ([https://web.archive.org/web/20221219143455/https://weirder.earth/@packbat/108815931937152540 archive.org]) critiques Disqordia's behavior ** Much of the Disqordia thread xey refer to is still available in [https://web.archive.org/web/20220816090453/https://akko.disqordia.space/notice/AMOna3GxzSqiJN6t9M archive.org]. * '''2022-07-04''' [https://jubi.life/@sixthhokage95/108592329213498710 jubi.life/@sixthhokage95] ([https://web.archive.org/web/20220816050124/https://cybre.space/@DangerDyke/108595663835969647 archive.org]): thread in which [https://disqordia.space/users/eris disqordia.space/users/eris] is clearly being deliberately (but subtly) provocative in a racist way; [https://cybre.space/@DangerDyke/ cybre.space/@DangerDyke] then defends eris ** [https://rage.love/@puf/108829477530153878 rage.love/@puf] ([https://web.archive.org/web/20221219225856/https://rage.love/@puf/108829477530153878 archive.org]) provides screenshots of that and additional bad behavior from eris ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] 6152391d5483c811b6539c69edb82911c5c1581a 754 752 2023-01-17T01:56:04Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] [[category:racism]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space * '''2022-11-29''' [https://weirder.earth/@packbat/109430760505891265 eldritch.cafe/@deadwitchflying] ([https://web.archive.org/web/20221219095655/https://weirder.earth/@packbat/109430760505891265 archive.org]) recommends blocking Disqordia: {{fmt/quote|Known shitheads who harass people on fediblock for calling them out on their bigotry and who gladly federate with fascists.}}. weirder.earth/@packbat notes that @eris "just today" boosted posts from {{fmt/quote|[[rdrama.cc]] and [[bae.st]], two famously racist instances}}. * '''2022-08-13''' [https://weirder.earth/@packbat/108815931937152540 weirder.earth/@packbat] ([https://web.archive.org/web/20221219143455/https://weirder.earth/@packbat/108815931937152540 archive.org]) critiques Disqordia's behavior ** Much of the Disqordia thread xey refer to is still available in [https://web.archive.org/web/20220816090453/https://akko.disqordia.space/notice/AMOna3GxzSqiJN6t9M archive.org]. * '''2022-07-04''' [https://jubi.life/@sixthhokage95/108592329213498710 jubi.life/@sixthhokage95] ([https://web.archive.org/web/20220816050124/https://cybre.space/@DangerDyke/108595663835969647 archive.org]): thread in which [https://disqordia.space/users/eris disqordia.space/users/eris] is clearly being deliberately (but subtly) provocative in a racist way; [https://cybre.space/@DangerDyke/ cybre.space/@DangerDyke] then defends eris ** [https://rage.love/@puf/108829477530153878 rage.love/@puf] ([https://web.archive.org/web/20221219225856/https://rage.love/@puf/108829477530153878 archive.org]) provides screenshots of that and additional bad behavior from eris ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] c1354a38cd356043b0ae2ca5c89aaec7400aa4da 765 754 2023-01-22T01:57:50Z Woozle 1 archive link removed by request wikitext text/x-wiki [[category:instance]] [[category:Akkoma]] [[category:blocked]] [[category:racism]] '''site''': [https://akko.disqordia.space Akkoma], [https://forum.disqordia.space/ Discourse] ==About== [[disqordia.space]] frequently seems to be involved in problematic interactions. TootCat blocked them for racism and harassment in December 2022. ==History== * '''2022-12-01''' TootCat blocks disqordia.space * '''2022-11-29''' [https://weirder.earth/@packbat/109430760505891265 eldritch.cafe/@deadwitchflying] recommends blocking Disqordia: {{fmt/quote|Known shitheads who harass people on fediblock for calling them out on their bigotry and who gladly federate with fascists.}}. weirder.earth/@packbat notes that @eris "just today" boosted posts from {{fmt/quote|[[rdrama.cc]] and [[bae.st]], two famously racist instances}}. * '''2022-08-13''' [https://weirder.earth/@packbat/108815931937152540 weirder.earth/@packbat] ([https://web.archive.org/web/20221219143455/https://weirder.earth/@packbat/108815931937152540 archive.org]) critiques Disqordia's behavior ** Much of the Disqordia thread xey refer to is still available in [https://web.archive.org/web/20220816090453/https://akko.disqordia.space/notice/AMOna3GxzSqiJN6t9M archive.org]. * '''2022-07-04''' [https://jubi.life/@sixthhokage95/108592329213498710 jubi.life/@sixthhokage95] ([https://web.archive.org/web/20220816050124/https://cybre.space/@DangerDyke/108595663835969647 archive.org]): thread in which [https://disqordia.space/users/eris disqordia.space/users/eris] is clearly being deliberately (but subtly) provocative in a racist way; [https://cybre.space/@DangerDyke/ cybre.space/@DangerDyke] then defends eris ** [https://rage.love/@puf/108829477530153878 rage.love/@puf] ([https://web.archive.org/web/20221219225856/https://rage.love/@puf/108829477530153878 archive.org]) provides screenshots of that and additional bad behavior from eris ==TootCat Admins== * [https://toot.cat/admin/instances/disqordia.space TC admin page] d6fcab2b87ab0b5c1c2768c85f0b111406d1a776 0 234 746 2023-01-17T01:01:18Z Woozle 1 Redirected page to [[Disqordia.space]] wikitext text/x-wiki #redirect [[disqordia.space]] 0d9e42b1a9c1578041ea8e585f2439c31f500c6d 10 235 755 2023-01-17T19:23:52Z Woozle 1 Created page with "&mdash;'''[[User:Woozle|W.]]'''" wikitext text/x-wiki &mdash;'''[[User:Woozle|W.]]''' 926ce1a0b79bde3d260b0180eb9a3c992a4f7d56 0 236 758 2023-01-17T19:30:29Z Woozle 1 Created page with "[[category:instance]] [[category:transmisia]] [[category:harassment]] ==History== * '''2023-01-24''' (block planned to go into effect) * '''2023-01-17''' [https://toot.cat/@ne..." wikitext text/x-wiki [[category:instance]] [[category:transmisia]] [[category:harassment]] ==History== * '''2023-01-24''' (block planned to go into effect) * '''2023-01-17''' [https://toot.cat/@news/109706098784877596 block planned for 1/24]: Transmisia, harassment, etc., * '''2022-12-23''' [https://rage.love/@admin/109561867581806363 rage.love/@admin] {{fmt/quote|FediBlock mastodon.world, queerphobia, domestic violence mention}} 9a7437e64d98e07fc19f43315819d82c989e84c1 0 237 759 2023-01-21T15:11:38Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] [[category:journalism]] [[category:transmisia]] '''site''': https://newsie.social/explore ==About== [[newsie.social]] is a Mastodon..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:journalism]] [[category:transmisia]] '''site''': https://newsie.social/explore ==About== [[newsie.social]] is a Mastodon instance. Although we have had positive interactions with some of its users, the admin ([https://newsie.social/@jeff @jeff]) appears not to understand the problem with "free speech" in fedi moderation. ==Dialogue== '''''2023-01-20 13:47''' [https://mspsocial.net/@mspsocialusers/109723023861427262 mspsocial.net/@mspsocialusers] said:'' <blockquote> Limiting newsie.social for not taking action on a transphobic user, and will move to suspension if their inaction persists. What is it about "journalism" instances that make them incapable of enforcing their own rules against transphobia? '''''2023-01-20 17:01''' [https://newsie.social/@jeff/109723786416370379 newsie.social/@jeff] (moderator) said:'' <blockquote> Because limiting speech you don't like or disagree with is limiting legitimate public discourse. If it's respectful and in good faith. </blockquote> </blockquote> There were many good replies to Jeff's comment. 422de7c647c81ab32aa8abea9ac893ebb01a8ec5 764 759 2023-01-21T17:57:54Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:journalism]] [[category:transmisia]] '''site''': https://newsie.social/explore ==About== [[newsie.social]] is a Mastodon instance. Although we have had positive interactions with some of its users, the admin ([https://newsie.social/@jeff @jeff]) apparently needed some education about the problem with "free speech" in fedi moderation. The problematic account has apparently been removed as of 2023-01-21 afternoon. ==Discussion== ===1=== '''2023-01-19 21:20''' [https://queer.party/@bri_seven/109719141443340152 queer.party/@bri_seven] posted screenshots of transphobic comments by [https://newsie.social/@tqwhite newsie.social/@tqwhite] (account now [https://web.archive.org/web/20221129101942/https://newsie.social/@tqwhite suspended]) ===2=== '''''2023-01-20 13:47''' [https://mspsocial.net/@mspsocialusers/109723023861427262 mspsocial.net/@mspsocialusers] said:'' <blockquote> Limiting newsie.social for not taking action on a transphobic user, and will move to suspension if their inaction persists. What is it about "journalism" instances that make them incapable of enforcing their own rules against transphobia? '''''2023-01-20 17:01''' [https://newsie.social/@jeff/109723786416370379 newsie.social/@jeff] (moderator) said:'' <blockquote> Because limiting speech you don't like or disagree with is limiting legitimate public discourse. If it's respectful and in good faith. </blockquote> </blockquote> There were many good replies to Jeff's comment. 07ce26c43e2fcbe22daa61d5ec9960862d34701e 0 238 760 2023-01-21T16:28:26Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] [[category:fascism]] [[category:homophobia]] [[category:ukraine]] [[category:blocked]] '''site''': {{ls/domain|ua-fediland.de}} ==A..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:fascism]] [[category:homophobia]] [[category:ukraine]] [[category:blocked]] '''site''': {{ls/domain|ua-fediland.de}} ==About== [[ua-fediland.de]] is a Mastodon instance which appears to have a problem with Nazis. At first<ref name=note1 />, it seemed that the Nazis were Russian propagandists signing up during blackouts, when the Ukrainian admins were not able to moderate, but later evidence<ref name=note2 /> suggests that this was just an excuse and the admins do in fact have Nazi sympathies. TootCat will be blocking them shortly. ==Footnotes== <references> <ref name=note1>'''2023-01-21 06:47''' [https://mastodon.art/@Curator/109727033755293169 mastodon.art/@Curator] {{fmt/quote|One of their moderators got back to my email. They're in Ukraine and can't moderate during the blackouts (understandably!), and the bots/spammers take advantage of the power outages (they're Russian) to sign up when they know they'll have maximum time to stay on the instance before getting moderated.}} <ref name=note2>'''2023-01-21 08:32''' [https://mastodon.art/@Curator/109727445911117353 mastodon.art/@Curator] {{fmt/quote|You may want to keep a block in place for this instance. / 'pidaras' is a slur in slavic languages that equates gay with child abuse. / The red black flag also has a nationalist and nazi-adjacent history...}} </ref> 8a8539ef88cab2312fac4bda0fae4d39867d9abf 761 760 2023-01-21T16:29:44Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:fascism]] [[category:homophobia]] [[category:ukraine]] [[category:blocked]] '''site''': {{ls/domain|ua-fediland.de}} ==About== [[ua-fediland.de]] is a Mastodon instance which appears to have a problem with Nazis. At first<ref name=note1 />, it seemed that the Nazis were Russian propagandists signing up during blackouts, when the Ukrainian admins were not able to moderate, but later evidence<ref name=note2 /> suggests that this was just an excuse and the admins do in fact have Nazi sympathies. TootCat will be blocking them shortly. ==Footnotes== <references> <ref name=note1>'''2023-01-21 06:47''' [https://mastodon.art/@Curator/109727033755293169 mastodon.art/@Curator] {{fmt/quote|One of their moderators got back to my email. They're in Ukraine and can't moderate during the blackouts (understandably!), and the bots/spammers take advantage of the power outages (they're Russian) to sign up when they know they'll have maximum time to stay on the instance before getting moderated.}}</ref> <ref name=note2>'''2023-01-21 08:32''' [https://mastodon.art/@Curator/109727445911117353 mastodon.art/@Curator] {{fmt/quote|You may want to keep a block in place for this instance. / 'pidaras' is a slur in slavic languages that equates gay with child abuse. / The red black flag also has a nationalist and nazi-adjacent history...}}</ref> </references> 14081d35cec9a3c20ad68647eb66a9f468319744 762 761 2023-01-21T16:33:01Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:fascism]] [[category:homophobia]] [[category:ukraine]] [[category:blocked]] '''site''': {{ls/domain|soc.ua-fediland.de}} ==About== [[ua-fediland.de]] is a Mastodon instance which appears to have a problem with Nazis. At first<ref name=note1 />, it seemed that the Nazis were Russian propagandists signing up during blackouts, when the Ukrainian admins were not able to moderate, but later evidence<ref name=note2 /> suggests that this was just an excuse and the admins do in fact have Nazi sympathies. TootCat blocked their domain completely at 2023-01-21 11:32 EST. ==Footnotes== <references> <ref name=note1>'''2023-01-21 06:47''' [https://mastodon.art/@Curator/109727033755293169 mastodon.art/@Curator] {{fmt/quote|One of their moderators got back to my email. They're in Ukraine and can't moderate during the blackouts (understandably!), and the bots/spammers take advantage of the power outages (they're Russian) to sign up when they know they'll have maximum time to stay on the instance before getting moderated.}}</ref> <ref name=note2>'''2023-01-21 08:32''' [https://mastodon.art/@Curator/109727445911117353 mastodon.art/@Curator] {{fmt/quote|You may want to keep a block in place for this instance. / 'pidaras' is a slur in slavic languages that equates gay with child abuse. / The red black flag also has a nationalist and nazi-adjacent history...}}</ref> </references> 7c2636730b95c3b60239dc7b078041ac22fee1f0 763 762 2023-01-21T17:40:32Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:fascism]] [[category:homophobia]] [[category:ukraine]] [[category:blocked]] '''site''': {{ls/domain|soc.ua-fediland.de}} ==About== [[ua-fediland.de]] is a Mastodon instance which appears to have a problem with Nazis. At first<ref name=note1 />, it seemed that the Nazis were Russian propagandists signing up during blackouts, when the Ukrainian admins were not able to moderate, but later evidence<ref name=note2 /> suggests that this was just an excuse and the admins do in fact have Nazi sympathies. It's not actually clear whether the domain and instance are owned/operated by Ukrainians / from Ukraine (whether citizens of or simply located in Ukraine). TootCat blocked their domain completely at 2023-01-21 11:32 EST. ==Footnotes== <references> <ref name=note1>'''2023-01-21 06:47''' [https://mastodon.art/@Curator/109727033755293169 mastodon.art/@Curator] {{fmt/quote|One of their moderators got back to my email. They're in Ukraine and can't moderate during the blackouts (understandably!), and the bots/spammers take advantage of the power outages (they're Russian) to sign up when they know they'll have maximum time to stay on the instance before getting moderated.}}</ref> <ref name=note2>'''2023-01-21 08:32''' [https://mastodon.art/@Curator/109727445911117353 mastodon.art/@Curator] {{fmt/quote|You may want to keep a block in place for this instance. / 'pidaras' is a slur in slavic languages that equates gay with child abuse. / The red black flag also has a nationalist and nazi-adjacent history...}}</ref> </references> f795c6761b3442dbd01786f0ca5afbb79a839ad2 0 1 766 685 2023-01-26T01:35:45Z Woozle 1 /* A Brief Directory */ git wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''MeW''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about * '''[[TootCat]]''': ** [[Toot.cat/CoC|Code of Conduct]] ** [[Toot.cat/CoJ|Code of Justice]] ** [[Help:Contribute]]: how to help keep us running ** [https://gitlab.com/tootcat/nixos-config TC's NixOS configuration] ** [[.cat]]: about the TLD * '''Directories''': ** {{l/cat|Instance}}s: *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe * '''miscellaneous''': ** [[Quote toot]]: a much-requested but also much-loathed feature ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> d5f944692a879d86b9367e5257b9a4d54971ca57 2 6 767 314 2023-01-27T19:43:07Z Woozle 1 wikitext text/x-wiki Me: * [https://toot.cat/@woozle toot.cat], of course * [https://woozalia.com creative stuff] * [https://wooz.dev software stuff] * [https://hypertwins.org family stuff] I also run [https://issuepedia.org Issuepedia], [https://htyp.org HTYP], and a few other specialty sites. ...and I host creative sites for two friends: * [https://outside-life.com Outside Life], a webcomic by drazahoib * [https://roastrabbit.com Roast Rabbit Productions], creative writing by Mek ==Popular Toots== * '''[https://toot.cat/@woozle/109433557495686417 2022-11-30]''' {{fmt/quote|Acid test for any social network or fedi instance: If you say "fuck you" to a Nazi, who gets banned?}} - This was during a peak of Twitter migration, which might explain why it seemed to resonate with so many people. Also, there was just a lot of activity happening at that time. <!--- ==Dialogues== * [[/octodon.social/@Megan]] --> 45bf1bf521f2bbc11d78a7a1017d5b2419acc50e 771 767 2023-02-02T23:55:52Z Woozle 1 wikitext text/x-wiki Me: * [https://toot.cat/@woozle toot.cat], of course * [https://woozalia.com creative stuff] * [https://wooz.dev software stuff] * [https://hypertwins.org family stuff] I also run [https://issuepedia.org Issuepedia], [https://htyp.org HTYP], and a few other specialty sites. ...and I host creative sites for two friends: * [https://outside-life.com Outside Life], a webcomic by drazahoib * [https://roastrabbit.com Roast Rabbit Productions], creative writing by Mek ==Popular Toots== * '''[https://toot.cat/@woozle/109433557495686417 2022-11-30]''' {{fmt/quote|Acid test for any social network or fedi instance: If you say "fuck you" to a Nazi, who gets banned?}} - This was during a peak of Twitter migration, which might explain why it seemed to resonate with so many people. Also, there was just a lot of activity happening at that time. * '''[https://toot.cat/@woozle/108897245523913683 2022-08-27]''' Photo of local "trans lives are sacred" mural <!--- ==Dialogues== * [[/octodon.social/@Megan]] --> d5131d35a603ae3eb6602dc129d4b62f5611ebe3 775 771 2023-02-09T13:52:54Z Woozle 1 wikitext text/x-wiki Me: * [https://toot.cat/@woozle toot.cat], of course * [https://woozalia.com creative stuff] * [https://wooz.dev software stuff] * [https://hypertwins.org family stuff] I also run [https://issuepedia.org Issuepedia], [https://htyp.org HTYP], and a few other specialty sites. ...and I host creative sites for two friends: * [https://outside-life.com Outside Life], a webcomic by drazahoib * [https://roastrabbit.com Roast Rabbit Productions], creative writing by Mek ==Popular Toots== * '''[https://toot.cat/@woozle/109433557495686417 2022-11-30]''' {{fmt/quote|Acid test for any social network or fedi instance: If you say "fuck you" to a Nazi, who gets banned?}} - This was during a peak of Twitter migration, which might explain why it seemed to resonate with so many people. Also, there was just a lot of activity happening at that time. * '''[https://toot.cat/@woozle/108897245523913683 2022-08-27]''' Photo of local "trans lives are sacred" mural ==Odd Discussions== * '''2023-02-02''' [https://toot.cat/@woozle/109795505300553305 Dems are held to a higher standard because they/we earned it...]: [https://genomic.social/@BlueWaver22 genomic.social/@BlueWaver22] blocked me for something I didn't actually say <!--- ==Dialogues== * [[/octodon.social/@Megan]] --> 6a256d1625240fad0bfd1be18ff5102456e063d1 785 775 2023-04-06T15:29:14Z Woozle 1 wikitext text/x-wiki <big>[[Woozle|Main Article]]</big> =Notes= Me: * [https://toot.cat/@woozle toot.cat], of course * [https://woozalia.com creative stuff] * [https://wooz.dev software stuff] * [https://hypertwins.org family stuff] I also run [https://issuepedia.org Issuepedia], [https://htyp.org HTYP], and a few other specialty sites. ...and I host creative sites for two friends: * [https://outside-life.com Outside Life], a webcomic by drazahoib * [https://roastrabbit.com Roast Rabbit Productions], creative writing by Mek ==Popular Toots== * '''[https://toot.cat/@woozle/109433557495686417 2022-11-30]''' {{fmt/quote|Acid test for any social network or fedi instance: If you say "fuck you" to a Nazi, who gets banned?}} - This was during a peak of Twitter migration, which might explain why it seemed to resonate with so many people. Also, there was just a lot of activity happening at that time. * '''[https://toot.cat/@woozle/108897245523913683 2022-08-27]''' Photo of local "trans lives are sacred" mural ==Odd Discussions== * '''2023-02-02''' [https://toot.cat/@woozle/109795505300553305 Dems are held to a higher standard because they/we earned it...]: [https://genomic.social/@BlueWaver22 genomic.social/@BlueWaver22] blocked me for something I didn't actually say <!--- ==Dialogues== * [[/octodon.social/@Megan]] --> af39eadcc8a3066879dba841b95979f3945f2f85 809 785 2023-06-26T12:49:35Z Woozle 1 /* Popular Toots */ wikitext text/x-wiki <big>[[Woozle|Main Article]]</big> =Notes= Me: * [https://toot.cat/@woozle toot.cat], of course * [https://woozalia.com creative stuff] * [https://wooz.dev software stuff] * [https://hypertwins.org family stuff] I also run [https://issuepedia.org Issuepedia], [https://htyp.org HTYP], and a few other specialty sites. ...and I host creative sites for two friends: * [https://outside-life.com Outside Life], a webcomic by drazahoib * [https://roastrabbit.com Roast Rabbit Productions], creative writing by Mek ==Popular Toots== * '''[https://toot.cat/@woozle/110607095417068327 2023-06-25]''' {{fmt/quote|"Can you explain this gap on your resume?"}}... * '''[https://toot.cat/@woozle/109433557495686417 2022-11-30]''' {{fmt/quote|Acid test for any social network or fedi instance: If you say "fuck you" to a Nazi, who gets banned?}} - This was during a peak of Twitter migration, which might explain why it seemed to resonate with so many people. Also, there was just a lot of activity happening at that time. * '''[https://toot.cat/@woozle/108897245523913683 2022-08-27]''' Photo of local "trans lives are sacred" mural ==Odd Discussions== * '''2023-02-02''' [https://toot.cat/@woozle/109795505300553305 Dems are held to a higher standard because they/we earned it...]: [https://genomic.social/@BlueWaver22 genomic.social/@BlueWaver22] blocked me for something I didn't actually say <!--- ==Dialogues== * [[/octodon.social/@Megan]] --> 714f0b1fe657d9ddeb903e7576089bbda5bd0d8e 0 239 768 2023-01-28T23:16:15Z Woozle 1 Created page with "[[category:instance]] [[category:silenced]] [[category:conservatism]] '''site''': https://republic.red/ ==About== [[republic.red]] is {{fmt/quote|a conservative friendly Masto..." wikitext text/x-wiki [[category:instance]] [[category:silenced]] [[category:conservatism]] '''site''': https://republic.red/ ==About== [[republic.red]] is {{fmt/quote|a conservative friendly Mastodon instance created for people who believe they are marginalized online for their political views}}. "Conservatism" is a classist/ableist philosophy which uses disinformation to create stochastic violence against outsiders, online and off, and TootCat has silenced this instance for that reason. ==Example== * '''2023-01-17''' [https://republic.red/@jeff/109705884788202433 republic.red/@jeff] {{fmt/quote|Often I read online that myocarditis is more common from Covid-19 than from one of the mRNA vaccines, without any proof. / Here is some ammunition against this falacy. Young males are 28x more likely to have myocarditis from the vaccine than from Covid-19. Here is the study:}} Jeff's claim is a misinterpretation of what the study found. e4857423b919fdae20f03b875676b6274984d169 0 70 769 402 2023-01-28T23:21:11Z Woozle 1 wikitext text/x-wiki * '''fedichive.tk''' = blocked for hostile data-collection, hostile interactions [https://web.archive.org/web/20190817050941/https://fedichive.tk/@fedichive/102630547432325773][https://mastodon.cloud/@dredmorbius/102634323367770340][https://afterlife.masto.host/@Pyretta/102630408436127536]([https://social.diskseven.com/@Jo/102630400997163398]) * '''socialnetwork.ninja''' - blocked 2019-04-23 because information indicated the instance is run by a police officer * '''bsd.moe''' * Our block list as of 2018-10-11 (I wish there was a way to export this in a better format; I had to do a lot of manual tidying): {| class="wikitable sortable" ! domain || status |- |prout.social |suspended |2 |- |hagra.net |suspended |1 |- |social.hatthieves.es |suspended |8 |- |gab.protohype.net |suspended |0 |- |fedichive.tk |suspended |1 |- |lets.saynoto.lgbt |suspended |2 |- |kiwifarms.is |suspended |0 |- |kiwifarms.net |suspended |0 |- |kiwifarms.cc |suspended |5 |- |gab.sleeck.eu |suspended |0 |- |gab.polaris-1.work |suspended |0 |- |not-develop.gab.com | |0 |- |exited.eu |suspended |2 |- |functor.pro |suspended |1 |- |gab.com |suspended |59 |- |develop.gab.com |suspended |6 |- |humblr.social |silenced |234 |- |freespeechextremist.com |suspended |133 |- |socialnetwork.ninja |suspended |0 |- |bsd.moe |suspended |14 |- |newjack.city |suspended |4 |- |pl.smuglo.li |suspended |160 |- |raki.social |suspended |3 |- |loli.estate |suspended |4 |- |eroma.rareome.ga |suspended |0 |- |polycule.club |suspended |5 |- |hiveway.net |silenced |30 |- |pridelands.io |suspended |1 |- |gs.archae.me |silenced |12 |- |post.mashek.net |suspended |1 |- |admins.town |silenced |23 |- |community.highlandarrow.com |suspended |25 |- |ediot.social |suspended |1 |- |mstdn.jp |silenced |2.96K |- |noagendasocial.com |silenced |699 |- |wogan.im |suspended |1 |- |anitwitter.com |silenced • rejecting media files |14 |- |freezepeach.xyz |silenced |41 |- |pawoo.net |silenced • rejecting media files |3.66K |- |social.heldscal.la |silenced |14 |- |social.troll.academy |silenced |19 |- |wrongthink.net |suspended |0 |- |unsafe.space |suspended |10 |- |gs.smuglo.li |suspended |90 |- |sealion.club |suspended |63 |- |gorf.club |suspended |1 |- |social.au2pb.net |suspended |1 |- |woofer.alfter.us |suspended |0 |- |social.headsca.la |suspended |0 |- |shitposter.club |suspended |201 |- |rainbowdash.net |suspended |12 |} 01ed8bd7b572ff567f54db1f4dce1703ba469f82 0 206 770 679 2023-02-02T20:01:51Z Woozle 1 wikitext text/x-wiki {{fmt/title|Commercial Activity & Self-Promotion}} <onlyinclude> We will not accept paid advertising. As members of a global community of sapient and compassionate beings, we reject the idea that possession of capitalist power-tokens entitles the holder to compel others. Accounts that exist primarily to promote for-profit<ref name=profit /> activity will be suspended without warning unless we have previously granted an exception. We do wish to support activities that support workers, creators, and communities. This includes but is not limited to: * independent artists/authors promoting or selling their own work or services, preferably through independent venues * individually or co-operatively-owned sales venues * individually or co-operatively-owned services Rule of thumb: any profile which includes phrases like "Looking for ''$thing''?" and then goes on to describe how they offer ''$thing'' (especially if they claim to have the best ''$thing'' in ''$area'') will probably be suspended on sight. </onlyinclude> ==Discussion== * '''2022-12-20''' [https://toot.cat/@woozle/109546094618870056 toot.cat/@woozle] {{fmt/quote|I need to update TC's policy-page to reflect this, but I draw a strong distinction between (a) an account which only exists to promote something, vs. (b) an account that interacts socially but also sometimes has things to promote.}} ==History== * '''2022-12-20''' revised to be more explicitly nurturing of independent creators ==Footnote== {{i/val|refs}} 164ac1941e35ea0069cbf7fcadca38e48951fc02 0 48 772 639 2023-02-06T01:44:42Z Woozle 1 /* Information */ wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. ===History=== It was founded by @polymerwitch and administrated by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. Recognizing the need for some more easily-referenced online presence, I set up a companion wiki (mew.toot.cat, what you're reading now) on 2018-03-30. * 2022: ** Viv has been massively helpful getting things upgraded. ** ash converted the server to NixOS, and created a failsafe deployment script. * 2020: Xenon Fiber joined the op team in 2020, replacing others who needed a break. ==Information== * [[/blocks/domain|domain blocks]] * [[/blocks/user|user blocks]] * [[/CoC]]: Code of Conduct * [[/CoJ]]: Code of Justice * [[/guidelines]]: some specifics * technical: [[/DNS]] ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Archives== * [[/2020]] * [[/2018]] * [[/2017]] 2dfa877ba6bcd5921f17a10317ad36e14f0a0b27 0 240 773 2023-02-06T01:46:55Z Woozle 1 Created page with "This list is far from complete; it's mainly for documenting any especially prize pazoozles we come across. * '''2023-02-05''' (silenced) [https://mastodon.social/@VoxofGod mas..." wikitext text/x-wiki This list is far from complete; it's mainly for documenting any especially prize pazoozles we come across. * '''2023-02-05''' (silenced) [https://mastodon.social/@VoxofGod mastodon.social/@VoxofGod]: [https://mastodon.social/@VoxofGod/109815233195979516] - pro-Putin propaganda; not listening to arguments, making snap negative judgements, hurling insults... 9d5790a72020581470c68d835c5185544058227d 774 773 2023-02-06T01:58:58Z Woozle 1 wikitext text/x-wiki This list does not even attempt to be comprehensive; it's mainly for documenting any especially prize pazoozles we come across. * '''2023-02-05''' (silenced) [https://mastodon.social/@VoxofGod mastodon.social/@VoxofGod]: [https://mastodon.social/@VoxofGod/109815233195979516] - pro-Putin propaganda; not listening to arguments, making snap negative judgements, hurling insults... 57bb8d4aee852f8f920d570e3bba521fd2079ec2 0 241 776 2023-02-09T20:42:46Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] [[category:transphobia]] ==Discussion== * '''2023-02-09 15:29''' [https://kolektiva.social/@YKantRachelRead/109836668497694836 kole..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:transphobia]] ==Discussion== * '''2023-02-09 15:29''' [https://kolektiva.social/@YKantRachelRead/109836668497694836 kolektiva.social/@YKantRachelRead] {{fmt/quote|I'm reading over the thread on mastodon.lol where the moderation team states that they won't allow people to spoil hogwarts legacy, and their main rationale seems to be, "but other instances might defederate from us if we allow this behavior to continue!"}} - Tempted to defederate from them for this anti-trans concern-trolling... * '''2023-02-09 14:37''' [https://mastodon.lol/@TheSunnyOne/109836463083876908 mastodon.lol/@TheSunnyOne] {{fmt/quote|They really do just think it's abut misgendering, don't they?}} ... {{fmt/quote|Oh, and once again equating sharing spoilers to actual harm.}} (includes screenshot of [https://mastodon.lol/@ColinRSykes Colin Sykes] calling the poster "scum" - fortunately he seems to have been suspended) 2f7c8d0981e884bf16f36616ba01ba54ef2d07ac 777 776 2023-02-09T20:49:08Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:transphobia]] ==Discussion== * '''2023-02-09 15:29''' [https://kolektiva.social/@YKantRachelRead/109836668497694836 kolektiva.social/@YKantRachelRead] {{fmt/quote|I'm reading over the thread on mastodon.lol where the moderation team states that they won't allow people to spoil hogwarts legacy, and their main rationale seems to be, "but other instances might defederate from us if we allow this behavior to continue!"}} * '''2023-02-09 15:20''' [https://mastodon.lol/@nathan/109836633022272265 mastodon.lol/@nathan] (admin) {{fmt/quote|Mastodon.lol will shut down on May 9, 2023, 3 months from today.}} * '''2023-02-09 14:37''' [https://mastodon.lol/@TheSunnyOne/109836463083876908 mastodon.lol/@TheSunnyOne] {{fmt/quote|They really do just think it's abut misgendering, don't they?}} ... {{fmt/quote|Oh, and once again equating sharing spoilers to actual harm.}} (includes screenshot of [https://mastodon.lol/@ColinRSykes Colin Sykes] calling the poster "scum" - fortunately he seems to have been suspended) 78a28fbb70a13297f6547f5a56ac579abc70ecb9 0 242 778 2023-02-24T01:27:43Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] [[category:Ukraine]] * '''site''': https://social.mykolayiv.dcomm.net.ua ==About== This is a Ukraine-based (.ua TLD) instance which..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:Ukraine]] * '''site''': https://social.mykolayiv.dcomm.net.ua ==About== This is a Ukraine-based (.ua TLD) instance which was apparently targeted on 2023-02-23 by Russian ops trying to discredit it and cause other instances to defederate from it. Someone created an account with the name "Adolf Hitler", and there was another account which appeared to be automatically following random fedi users. TootCat blocked both of those accounts but took no action against the instance. ==Posts== * '''2023-02-23''' [https://social.mykolayiv.dcomm.net.ua/@insiderua social.mykolayiv.dcomm.net.ua/@insiderua] {{fmt/quote| Thank you, all, for a report on the account with the name Hitler – the account was suspended [..] As a moderator, I have checked the account (in fact three accounts were created today) – most likely it is part of Russian hybrid warfare as accounts pretended to be Ukrainians, but digital traces (the interface is Russian, Russian naming of other accounts, Russian hostname while IP location is in Warsaw) [..] Please, be careful, and thanks, for reporting!}} 7d2ee61559b6166952e3e5e218d7bcde4e293f45 0 243 779 2023-03-01T21:47:55Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] ==Actions== * '''2023-03-01''' We had this instance blocked because of a supposed ableist slur on the /about/more page, but it wasn..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] ==Actions== * '''2023-03-01''' We had this instance blocked because of a supposed ableist slur on the /about/more page, but it wasn't clear exactly what the slur was and was unable to find anything problematic on their about page (/about/more now just redirects to /about). The suspension was done so long ago that there was no indication as to who did it. Suspension removed. -W. a9c330ae1b0624a8063afb25b6e6de39ef7bc97c 0 244 780 2023-03-22T00:10:48Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] ==Notes== Mastodon instance of the CyberPeace Institute. An [[anonoboost]] fedi user notes: {{fmt/quote|I always considered them a..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] ==Notes== Mastodon instance of the CyberPeace Institute. An [[anonoboost]] fedi user notes: {{fmt/quote|I always considered them a thinly-veiled LEA front and Microsoft's propaganda outlet. Blocked the whole domain for good measure, but you draw your own conclusions.}} bc0a4bca0a5e97d9ed2bd6b6e34d6c3ab7f18096 0 245 781 2023-03-22T00:13:30Z Woozle 1 Created page with "[[category:policy]] We're using the phrase [[anonoboost]] when referring to someone who made a post that cannot be boosted (or who requested no boosting), implying that they d..." wikitext text/x-wiki [[category:policy]] We're using the phrase [[anonoboost]] when referring to someone who made a post that cannot be boosted (or who requested no boosting), implying that they do not wish the post to be publicized. We will only quote from such posts and not link to them. Identifying information will not be included in quotes. 8f8be825eac2c0ebf8876c4d4d60d5f9baa12837 782 781 2023-03-22T00:14:16Z Woozle 1 wikitext text/x-wiki [[category:policy]] We're using the phrase [[anonoboost]] when referring to someone who made a post that cannot be boosted (or who requested no boosting), implying that they do not wish the post to be publicized. We will only quote from such posts and not link to them. Identifying information will not be included in quotes. The user is known to us (hence not "anonymous"), but we are keeping them anonymous in our boosting of the information they posted. 9f88150e53a53c0e3038c75c87bd502ceab60f65 783 782 2023-03-22T00:15:07Z Woozle 1 wikitext text/x-wiki [[category:policy]] [[category:terminology]] We're using the phrase [[anonoboost]] when referring to someone who made a post that cannot be boosted (or who requested no boosting), implying that they do not wish the post to be publicized. We will only quote from such posts and not link to them. Identifying information will not be included in quotes. The user is known to us (hence not "anonymous"), but we are keeping them anonymous in our boosting of the information they posted. 8b79f43b12d9d08e6a8b80bd8a4f054d1e1688e0 0 44 784 396 2023-04-06T15:28:11Z Woozle 1 wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://lor.sh/@dump_stack dump_stack] | {{ls/domain|lor.sh}} | Mastodon | * '''2020-02-24''' [https://lor.sh/@dump_stack/103715838645490658] "people have anti-homeless attitudes because most of the time being homeless is a choice not a matter of chance." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |- | [https://zirk.us/@dambaras dambaras] ([https://chass.ncsu.edu/people/dambaras/ David Ambaras]) | {{ls/domain|zirk.us}} | Mastodon | * '''2023-04-06''' [https://web.archive.org/web/20230406141102/https://zirk.us/@dambaras/110149627484335327 response]: replying to my post with insult, and never backing down |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li. '''Update 2018-10-07''': They have now been blocked after a report from a known user.</ref> </references> d8785aa42fecc984d631f35e7c370951a4342db0 0 246 786 2023-05-01T00:03:47Z Woozle 1 Created page with "[[category:Mastodon]] [[category:instance]] '''site''': {{ls/domain|hachyderm.io}} ==Posts About== * '''2023-04-30''' [https://dotart.blog/welshpixie/fedi-famous Fedi Famous]..." wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] '''site''': {{ls/domain|hachyderm.io}} ==Posts About== * '''2023-04-30''' [https://dotart.blog/welshpixie/fedi-famous Fedi Famous] * '''2023-04-26''' [https://dotart.blog/dotart-blog/silencing-hachyderm Silencing Hachyderm] 0a43fd1bcba5bb672e247fd566ac356010e0d371 787 786 2023-05-01T00:09:09Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] '''site''': {{ls/domain|hachyderm.io}} ==Posts About== * '''2023-04-30''' [https://dotart.blog/welshpixie/fedi-famous Fedi Famous] ([https://mastodon.art/@welshpixie/110289480412294337 via]) * '''2023-04-26''' [https://dotart.blog/dotart-blog/silencing-hachyderm Silencing Hachyderm] 09d7e8468c67e4806ea89ab08efd26774773e72f 0 225 788 732 2023-05-12T15:52:13Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': https://c.im/about ==Discussion== * '''2022-12-30''' <s>[https://oliphant.social/@Blackfist/109597851412606231 oliphant.social/@Blackfist]</s> (post gone) apparently got banned for merely ''alluding'' to racism. It seems likely they are using the racist definition of "racism", i.e. the opposite of what it actually means. 13992df08583f671d89c737c31a00174d7ca41f6 12 247 789 2023-05-28T14:31:02Z Woozle 1 Created page with "There has been basically no interest in anyone else editing the wiki, so the only wiki help page I have put together so far is for for my own reference: * [[Help:Admin]]" wikitext text/x-wiki There has been basically no interest in anyone else editing the wiki, so the only wiki help page I have put together so far is for for my own reference: * [[Help:Admin]] b961bc456594a1d17966fe71f8f207c9eecfaa10 12 248 790 2023-05-28T14:37:27Z Woozle 1 Created page with "==Editing== * '''Q: How do I enable HTML in my posts?''' ** '''A:''' In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an i..." wikitext text/x-wiki ==Editing== * '''Q: How do I enable HTML in my posts?''' ** '''A:''' In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to let you choose which type of markup to use. Select "Markdown" or "HTML". (I'm working on adding a screenshot.) There's also a user-option to set the default type. ==Accounts== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. d50da3105c834036c96f2fe03f3b386edaef3a0c 794 790 2023-05-28T14:46:40Z Woozle 1 wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Accounts== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. 41495e91df9173481323806483356110eadd2d1c 814 794 2023-07-02T18:02:39Z Woozle 1 wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to find solutions; see {{l/sub|safe space}} for more. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be hashtagged. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. 4347dcda5e1a203eee81e8c8db80d5aa7ee851e1 12 3 791 196 2023-05-28T14:38:04Z Woozle 1 wikitext text/x-wiki ==Help Topics== <big> * [[Help:TootCat]]: how to use TootCat (the Mastodon Glitch Edition site) * [[Help:Wiki]]: wiki help ** [[Help:Admin]]: wiki administration </big> 0062e2a9686f2db609af37c3bd8d1b64edb026cf 6 249 792 2023-05-28T14:43:44Z Woozle 1 [[category:screenshot]] [[category:TootCat]] wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:TootCat]] 23d7c526fa38733ec1ce4199566fa92c39f5beb8 12 250 793 2023-05-28T14:46:28Z Woozle 1 Created page with "* '''Q: How do I enable HTML in my posts?''' ** '''A:''' In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to let y..." wikitext text/x-wiki * '''Q: How do I enable HTML in my posts?''' ** '''A:''' In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to let you choose which type of markup to use. Select "Markdown" or "HTML". *** There's also a user-option to set the default type. In this screenshot, the markup-type is shown as a down-arrow icon because I've selected "Markdown", which also allows HTML: [[File:2023-05-28 at 10-42-24 Toot.Cat.screen.post editing area.png]] 9c91e568da6f1f40fe115846ba52faf86f883641 796 793 2023-05-28T15:56:12Z Woozle 1 wikitext text/x-wiki * '''Q: How do I enable HTML in my posts?''' ** '''A:''' In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to let you choose which type of markup to use. Select "Markdown" or "HTML". *** There's also a user-option to set the default type. In this screenshot, the markup-type is shown as a down-arrow icon because I've selected "Markdown", which also allows HTML: [[File:2023-05-28 at 10-42-24 Toot.Cat.screen.post editing area.png]] The default markup type can be set in [https://toot.cat/settings/preferences/other preferences/other]: [[File:Screenshot 2023-05-28 at 11-12-57 Preferences - Toot.Cat.screen.markup options.png]] f134413e2a38f474bc905cc29be27afd219d920d 798 796 2023-05-28T17:23:52Z Woozle 1 wikitext text/x-wiki * '''Q: How do I enable HTML in my posts?''' ** '''A:''' In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to let you choose which type of markup to use. Select "Markdown" or "HTML". *** There's also a user-option to set the default type. In this screenshot, the markup-type is shown as a down-arrow icon because I've selected "Markdown", which also allows HTML: [[File:2023-05-28 at 10-42-24 Toot.Cat.screen.post editing area.png]] If that icon does not appear, you can enable it in the UI settings dialog (click the gears-icon at the top of the left column) -- check the "show content choice" checkbox: [[File:2023-05-28 at 13-17-29.screen.TC settings dialog.show markup type.png]] The default markup type can be set in [https://toot.cat/settings/preferences/other preferences/other]: [[File:Screenshot 2023-05-28 at 11-12-57 Preferences - Toot.Cat.screen.markup options.png]] 924369fbab27b977d01f8e3663b02e2f0a24874e 800 798 2023-05-28T18:03:16Z Woozle 1 wikitext text/x-wiki {{fmt/title|Using HTML in TootCat}} The Glitch Edition of Mastodon supports enhanced formatting of your posts by use of Markdown and HTML. ==FAQ== * '''Q: How do I enable HTML in my posts?''' ** '''A:''' See [[/enabling|enabling HTML editing]] * '''Q: What HTML and Markdown can I use in my posts?''' ** '''A:''' See {{l/sub|formatting}}. ==Support== Note that some clients don't display text-formatting properly. Known issues as of 2023-05-28: * Metatext: no bold/italic * Tooot: no bold/italic * Trunk Mastodon: only links work; lists may get condensed to a single paragraph All of them render links properly, but some may insert "safety text" to warn you when the link text does not match the domain being linked (I think the assumption is that all links are auto-linked URLs, which is probably true with Trunk Mastodon). 069f8f93a07eb365f4a004e221dabdcc302eddc9 801 800 2023-05-28T18:04:22Z Woozle 1 wikitext text/x-wiki {{fmt/title|Using HTML in TootCat}} The Glitch Edition of Mastodon (MGE) supports enhanced formatting of your posts by use of Markdown and HTML. ==FAQ== * '''Q: How do I enable HTML in my posts?''' ** '''A:''' See [[/enabling|enabling HTML editing]] * '''Q: What HTML and Markdown can I use in my posts?''' ** '''A:''' See {{l/sub|formatting}}. ==Support== Note that some clients don't display text-formatting properly. Known issues as of 2023-05-28: * Metatext: no bold/italic * Tooot: no bold/italic * Trunk Mastodon: only links work; lists may get condensed to a single paragraph All of them render links properly, but some may insert "safety text" to warn you when the link text does not match the domain being linked (I think the assumption is that all links are auto-linked URLs, which is probably true with Trunk Mastodon). MGE does insert this text by default, but you can turn it off in the UI options dialog. 49c0b841a02a902a61688902f60aeed8e077cef8 6 251 795 2023-05-28T15:14:24Z Woozle 1 [[category:screenshot]] [[category:TootCat]] wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:TootCat]] 23d7c526fa38733ec1ce4199566fa92c39f5beb8 6 252 797 2023-05-28T17:22:04Z Woozle 1 [[category:screenshot]] [[category:TootCat]] wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:TootCat]] 23d7c526fa38733ec1ce4199566fa92c39f5beb8 12 253 799 2023-05-28T17:42:27Z Woozle 1 Created page with "{{fmt/title|How to enable HTML and Markdown in your posts}} In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to l..." wikitext text/x-wiki {{fmt/title|How to enable HTML and Markdown in your posts}} In the web UI, under the edit box between the post-privacy globe icon and the CW icon there should be an icon to let you choose which type of markup to use (if it's not there, see "enable the icon" below). Select "Markdown" or "HTML". In this screenshot, the markup-type is shown as a down-arrow icon because I've selected "Markdown", which also allows HTML: [[File:2023-05-28 at 10-42-24 Toot.Cat.screen.post editing area.png]] ==Enable the Icon== If the content-markup-choice icon does not appear, you can enable it in the UI settings dialog (click the gears-icon at the top of the left column) -- check the "show content choice" checkbox: [[File:2023-05-28 at 13-17-29.screen.TC settings dialog.show markup type.png]] ==Set a Default== If you expect to want Markdown or HTML a lot, you can change the default in [https://toot.cat/settings/preferences/other preferences/other]: [[File:Screenshot 2023-05-28 at 11-12-57 Preferences - Toot.Cat.screen.markup options.png]] f3054e08fb1fbb36365b9eefc28b394ab6e55af3 12 254 802 2023-05-28T18:14:53Z Woozle 1 Created page with "{{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and it's ofte..." wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and it's often useful to be able to intermix them -- so we recommend using the Markdown option rather than HTML only. The following applies to both choices; see {{l/same|Markdown}} for syntax that only works in the Markdown option. ==Tags== <syntaxhighlight lang=html> Character formatting: <b>bold</b> <i>italic</i> Lists: <ul><li>item one<li>item two</ul> <ol<li>item one<li>item two</ol> Links: <a href="URL">display text</a> #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link NOT SUPPORTED: <pre>, <tt> </syntaxhighlight> (I put the # outside of the link so it looks a little different from a regular hashtag.) f995337ab8f367c607b4431c7066b90bfd1e4514 803 802 2023-05-28T18:36:48Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and it's often useful to be able to intermix them -- so we recommend using the Markdown option rather than HTML only. The following applies to both choices; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== <syntaxhighlight lang=html> Character formatting: <b>bold</b> <i>italic</i> <u>underline</u> Lists: <ul><li>item one<li>item two</ul> <ol<li>item one<li>item two</ol> Links: <a href="URL">display text</a> #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> (I put the # outside of the link so it looks a little different from a regular hashtag.) f0f8dfafc37c9c6453eba9cb6586bbbb3fc62c0a 805 803 2023-05-28T18:43:37Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== <syntaxhighlight lang=html> Character formatting: <b>bold</b> <i>italic</i> <u>underline</u> Lists: <ul><li>item one<li>item two</ul> <ol<li>item one<li>item two</ol> Links: <a href="URL">display text</a> #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> (I put the # outside of the link so it looks a little different from a regular hashtag.) 5fbe6c3f7a4c2aadf10f83a17d36db39952a06af 807 805 2023-05-28T21:33:54Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== <syntaxhighlight lang=html> Character formatting: <b>bold</b> <i>italic</i> <u>underline</u> ^superscript -- e.g.: E=MC² _subscript -- e.g.: H₂O Lists: <ul><li>item one<li>item two</ul> <ol<li>item one<li>item two</ol> Links: <a href="URL">display text</a> #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> (I put the # outside of the link so it looks a little different from a regular hashtag.) fb9b7a038c59e21b51c86054665c3274820fc5f3 12 255 804 2023-05-28T18:42:15Z Woozle 1 Created page with "{{fmt/title|formatting posts with Markdown}} Remember that anything that works with the [[../|HTML option]] will also work with the Markdown option! <syntaxhighlight lang=md>..." wikitext text/x-wiki {{fmt/title|formatting posts with Markdown}} Remember that anything that works with the [[../|HTML option]] will also work with the Markdown option! <syntaxhighlight lang=md> ===================== Character formatting: ===================== **bold** *italic* ~~strike~~ _underline_ [link text](URL) - must be full URL with protocol ====== Lists: ====== * bullet item one * bullet item two * sub-item for item 2 (2 spaces per indent) * bullet item three 1. numbered list item 1 2. numbered list item 2 ============ Fixed-pitch: ============ `inline fixed-pitch text` ``` multiline fixed-pitch text ``` ============ Text blocks: ============ # Header 1 ## Header 2 ### Header 3 > quote-indented text </syntaxhighlight> ==Further Reading on Markdown== Note that TootCat only supports a small ''subset'' of Markdown. * [[wikipedia:Markdown|Wikipedia]] * [https://daringfireball.net/projects/markdown/ official site] * [https://www.markdownguide.org/ Markdown Guide] 4c3e460051be0dad9c4bee6de1ef9ca66580e164 806 804 2023-05-28T21:32:08Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with Markdown}} Remember that anything that works with the [[../|HTML option]] will also work with the Markdown option! <syntaxhighlight lang=md> ===================== Character formatting: ===================== **bold** *italic* ~~strike~~ _underline_ [link text](URL) - must be full URL with protocol ^superscript -- like: E=MC^2 I don't know how to turn it off without a space. You can even do supersuperscript: Normal^super^hyper makes "hyper" look like a superscript on "super" -- both higher and smaller ====== Lists: ====== * bullet item one * bullet item two * sub-item for item 2 (2 spaces per indent) * bullet item three 1. numbered list item 1 2. numbered list item 2 ============ Fixed-pitch: ============ `inline fixed-pitch text` ``` multiline fixed-pitch text ``` ============ Text blocks: ============ # Header 1 ## Header 2 ### Header 3 > quote-indented text </syntaxhighlight> ==Further Reading on Markdown== Note that TootCat only supports a small ''subset'' of Markdown. * [[wikipedia:Markdown|Wikipedia]] * [https://daringfireball.net/projects/markdown/ official site] * [https://www.markdownguide.org/ Markdown Guide] 02fb7f8ba3587ea7774619836d37cd0b825a46d2 0 256 808 2023-06-04T12:09:39Z Woozle 1 Created page with "[[category:instance]] {{fmt/title|nerd.town}} We had this blocked for awhile due to slurs and fash, but apparently the problem was signup-bots which the site's admin was havi..." wikitext text/x-wiki [[category:instance]] {{fmt/title|nerd.town}} We had this blocked for awhile due to slurs and fash, but apparently the problem was signup-bots which the site's admin was having difficulty preventing. He eventually got it under control, and we unblocked them. The public posts from admin's end of the discussion have since been deleted; in a followers-only post on 2023-06-04, he notified us that the problem seemed to be under control. (A screenshot of the deleted posts are in our [https://gitlab.com/tootcat/moderation/-/blob/main/screenshots/2023-05-22.screen_Ben_Lovell___socksy_toot.cat_.png private moderation repo].) Relevant public posts: * [https://toot.cat/@news/110413423553610876 2023-05-22 @news] * [https://toot.cat/@news/110399082071955078 2023-05-20 @news] announcing the domain block 3d694e93d91049bffe9099828ac8101084d3ae41 0 236 810 758 2023-06-27T17:07:33Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:transmisia]] [[category:harassment]] [[category:blocked]] ==History== * '''2023-01-24''' (block planned to go into effect) * '''2023-01-17''' [https://toot.cat/@news/109706098784877596 block planned for 1/24]: Transmisia, harassment, etc., * '''2022-12-23''' [https://rage.love/@admin/109561867581806363 rage.love/@admin] {{fmt/quote|FediBlock mastodon.world, queerphobia, domestic violence mention}} ef753312fad0c662b257a734c624df2892b38a6e 811 810 2023-06-27T17:27:40Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:transmisia]] [[category:harassment]] [[category:blocked]] ==History== * '''2023-06-27''' notching this back to a "silence" because, well, [https://toot.cat/@catvalente@mastodon.world Cat Valente]. If they become a problem, though, this could revert to "block". ** ...and maybe someone can convince Cat to find a better-moderated instance? * '''2023-01-24''' (block planned to go into effect) * '''2023-01-17''' [https://toot.cat/@news/109706098784877596 block planned for 1/24]: Transmisia, harassment, etc., * '''2022-12-23''' [https://rage.love/@admin/109561867581806363 rage.love/@admin] {{fmt/quote|FediBlock mastodon.world, queerphobia, domestic violence mention}} 93f6f31724fba8510b8004e15b817f624837fc45 812 811 2023-06-27T17:27:57Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:transmisia]] [[category:harassment]] [[category:blocked]] ==History== * '''2023-06-27''' notching this back to a "silence" because, well, [https://toot.cat/@catvalente@mastodon.world Cat Valente]. If instance becomes a problem again, though, this could revert to "block". ** ...and maybe someone can convince Cat to find a better-moderated instance? * '''2023-01-24''' (block planned to go into effect) * '''2023-01-17''' [https://toot.cat/@news/109706098784877596 block planned for 1/24]: Transmisia, harassment, etc., * '''2022-12-23''' [https://rage.love/@admin/109561867581806363 rage.love/@admin] {{fmt/quote|FediBlock mastodon.world, queerphobia, domestic violence mention}} f8c76c7f4515345a80e2aec15b66dab669f795a7 0 257 813 2023-06-27T18:31:21Z Woozle 1 Created page with "[[category:instance]] [[category:mastodon]] ==Notes== * '''2023-06-18''' [https://mstdn.social/@stux/110567524159195690 @stux] notes his intention to initially allow federatio..." wikitext text/x-wiki [[category:instance]] [[category:mastodon]] ==Notes== * '''2023-06-18''' [https://mstdn.social/@stux/110567524159195690 @stux] notes his intention to initially allow federation with Meta projects; discussion ensues. e5e361d07729c576475ddd31edc77772f5fcc1d7 10 258 815 2023-07-02T18:07:03Z Woozle 1 Created page with "[https://toot.cat/{{{1}}} {{{1}}}]" wikitext text/x-wiki [https://toot.cat/{{{1}}} {{{1}}}] 23e9fdc53e7f26a29006e717338f649658e0f643 0 259 816 2023-07-02T18:38:12Z Woozle 1 Created page with "===History=== TootCat was founded in 2017 by @polymerwitch and administered by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [..." wikitext text/x-wiki ===History=== TootCat was founded in 2017 by @polymerwitch and administered by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. ==Timeline (newest to oldest)== * 2022: ** ash converted the server to NixOS, and created a failsafe deployment script. ** Viv has been massively helpful getting things upgraded. ** Dan has automated some processes and also handles upgrades. ** Ruby and Stephanie joined the mod team, helping to deal with the first massive Twitterfail influx (among other things). * 2020: Xenon Fiber joined the op team in 2020, replacing others who needed a break. * 2018-03-30: Recognizing the need for some more easily-referenced online presence, I ([[@Woozle]]) set up this companion wiki (mew.toot.cat, what you're reading now). * 2018-01-01: Ownership is handed over to @Woozle. Somewhere I have a link to an archive of the first Toot on TootCat... 1df9ba5f74feca6e068e9fa61af7957c1cb05ce8 0 66 817 449 2023-07-02T18:44:59Z Woozle 1 Woozle moved page [[Toot.cat/guidelines]] to [[Toot.cat/CoC/red flags]]: reorganizing wikitext text/x-wiki ==Red Flags== TootCat will block individuals and instances who persistently raise these flags: * '''Punching down''': it's not okay to punch down, and it's okay to call out people who are doing it. ** In general, "punching down" means criticizing people who are underprivileged or have less power than you. ** Examples: *** making fun of nontraditional pronouns [https://social.panthermodern.net/@0x00/103754842757342400] *** deliberately misgendering someone, especially a trans person * '''Using "free speech" as an excuse''' ({{l/ip|free speech trolling}}) ** {{l/ip|Freedom of speech}} just means ''the government'' can't stop you from saying things. ** It does not mean freedom from consequences if you say something obnoxious or hurtful. ** It does not mean that any private venue is required to give you a platform. ** One opinion is ''not'' as good/valid as any other ''if one of them is harmful''. *** Inaccuracy of factual details is often (but not always) a cause of harm, as it can lead to maltreatment of others. [[issuepedia:Truth/evidenced|Truth]] matters. 2f453a26e1dbc4627e0241058d770ed2869d54eb 0 260 818 2023-07-02T18:45:00Z Woozle 1 Woozle moved page [[Toot.cat/guidelines]] to [[Toot.cat/CoC/red flags]]: reorganizing wikitext text/x-wiki #REDIRECT [[Toot.cat/CoC/red flags]] 88ff1424a04ddc1fb84c4b1002f0d6a6a7eb2d99 0 62 819 680 2023-07-02T18:47:28Z Woozle 1 /* General */ wikitext text/x-wiki =Code of Conduct= ==Meta== This is not a contract. This is a guideline to help you understand how we, as a community, see and evaluate different kinds of behavior. We will always try to leave room for honest mistakes and misunderstandings, but we reserve the right to act without regard to strict or exacting interpretation of these guidelines. They are a statement of intention, and they are intended to reflect the views of the TootCat community. If you have comments or questions, please feel free to reach out to the TootCat Uberwensch ([https://toot.cat/@woozle @woozle]) whether or not you are a TootCat member. ^.^ ==General== As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users. We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination. We try to empower our users and encourage them to act against any abuses of the Code of Conduct, in order to ensure that TootCat remains an oppression-free experience. Examples of unacceptable behavior include: <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>{{l/sub|red flags}} (a couple of specific examples)</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Activity / Self-Promotion ('''[[/self-promo|&gt;&gt;]]''')== {{i/sub|self-promo}} ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> ==Footnotes== {{i/val|page={{PAGENAME}}/self-promo|refs}} 40408a49e3417f27eac29074bbafb3af997a1471 0 48 820 772 2023-07-02T18:47:57Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. * '''{{l/sub|history}}''': a brief and occasionally-updated history of our instance * '''{{l/sub|CoC}}: Code of Conduct * [[/blocks/domain|domain blocks]]: some details * [[/blocks/user|user blocks]] * [[/CoJ]]: Code of Justice * technical: [[/DNS]] ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Archives== * [[/2020]] * [[/2018]] * [[/2017]] 2c6614843c463ee826800cfcb6460399fa547539 846 820 2023-07-03T15:31:57Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. * '''[[Help:TootCat|TootCat Help]]''' and FAQ * '''{{l/sub|history}}''': a brief and occasionally-updated history of our instance * '''{{l/sub|CoC}}: Code of Conduct * [[/blocks/domain|domain blocks]]: some details * [[/blocks/user|user blocks]] * [[/CoJ]]: Code of Justice * technical: [[/DNS]] ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Archives== * [[/2020]] * [[/2018]] * [[/2017]] 85c1ae9a75380d019c86d32774131d5716cdc583 0 138 821 450 2023-07-02T18:50:09Z Woozle 1 Changed redirect target from [[Toot.cat/guidelines]] to [[Toot.cat/CoC/red flags]] wikitext text/x-wiki #REDIRECT [[Toot.cat/CoC/red flags]] 88ff1424a04ddc1fb84c4b1002f0d6a6a7eb2d99 0 259 822 816 2023-07-02T18:50:32Z Woozle 1 wikitext text/x-wiki ===History=== TootCat was founded in 2017 by @polymerwitch and administered by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. ==Timeline (newest to oldest)== * 2022: ** ash converted the server to NixOS, and created a failsafe deployment script. ** Viv has been massively helpful getting things upgraded. ** Dan has automated some processes and also handles upgrades. ** Ruby and Stephanie joined the mod team, helping to deal with the first massive Twitterfail influx (among other things). * 2020: Xenon Fiber joined the op team in 2020, replacing others who needed a break. * [[Toot.cat/2018|2018]]-03-30: Recognizing the need for some more easily-referenced online presence, I ([[@Woozle]]) set up this companion wiki (mew.toot.cat, what you're reading now). * [[Toot.cat/2017|2017]]-12-31: Ownership is handed over to @Woozle. Somewhere I have a link to an archive of the first Toot on TootCat... c61f0dfcf930411366c05f69bf59f3879bc298e7 6 261 823 2023-07-02T18:52:45Z Woozle 1 one of the Glitch Edition mastodon graphics wikitext text/x-wiki == Summary == one of the Glitch Edition mastodon graphics c3d92d859b74e7a81843f03096fa07a08fc1da1c 6 262 824 2023-07-02T18:54:17Z Woozle 1 one of the Glitch Edition mastodon graphics wikitext text/x-wiki == Summary == one of the Glitch Edition mastodon graphics c3d92d859b74e7a81843f03096fa07a08fc1da1c 6 263 825 2023-07-02T18:55:17Z Woozle 1 one of the Glitch Edition mastodon graphics wikitext text/x-wiki == Summary == one of the Glitch Edition mastodon graphics c3d92d859b74e7a81843f03096fa07a08fc1da1c 6 264 826 2023-07-02T18:56:42Z Woozle 1 the default user avatar on standard Mastodon and Glitch Edition wikitext text/x-wiki == Summary == the default user avatar on standard Mastodon and Glitch Edition 340bceb151e1183eb688a9f424549c403148869a 12 248 827 814 2023-07-02T18:59:46Z Woozle 1 wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ** '''A:''' Absolutely! We welcome all species. Especially ferrets, wombats, possums, and capybaras. But dogs are cool too. ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to find solutions; see {{l/sub|safe space}} for more. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be CWed. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** Note that for those who don't like using CWs, another alternative is to use hashtags -- which can be filtered against by people who don't want to see certain types of content. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. 7e4d7211aea2a7e3c3eff62d436e66263783037d 843 827 2023-07-02T19:37:34Z Woozle 1 wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ** '''A:''' Absolutely! We welcome all species. Especially ferrets, wombats, possums, and capybaras. But dogs are cool too. ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to help find solutions. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be CWed. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** Note that for those who don't like using CWs, another alternative is to use hashtags -- which can be filtered against by people who don't want to see certain types of content. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. d74a09bfbf1bf6e6b1b0d9cc1d7d6015d4ad9a8a 845 843 2023-07-02T20:37:54Z Woozle 1 /* How to Social */ wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ** '''A:''' Absolutely! We welcome all species. Especially ferrets, wombats, possums, and capybaras. But dogs are cool too. ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' ** '''A:''' See [[Toot.cat/CoC|the CoC]]. * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to help find solutions. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be CWed. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** Note that for those who don't like using CWs, another alternative is to use hashtags -- which can be filtered against by people who don't want to see certain types of content. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. 43186f3749e2135996fc242f4ffd6e89d55eb7e8 850 845 2023-07-03T19:20:22Z Woozle 1 /* How to Social */ wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ** '''A:''' Absolutely! We welcome all species. Especially ferrets, wombats, possums, and capybaras. But dogs are cool too. ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' ** '''A:''' See [[Toot.cat/CoC|the CoC]]. * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to help find solutions. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. *** '''Note''' that you can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be CWed. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** Note that for those who don't like using CWs, another alternative is to use hashtags -- which can be filtered against by people who don't want to see certain types of content. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. faeca772986b15c0b610e48fa1af817a24e3238e 852 850 2023-07-04T17:23:27Z Woozle 1 wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Constrants== * '''Q: Do you have any language requirements (e.g. only post in English)?''' ** '''A:''' Any language is fine! *** We will use translation tools as needed to spot-check content, but we largely rely on other speakers to report users who are being problematic in languages we don't speak. *** For example: We had a small influx of Chinese users in 2022 when the PRC blocked access to Twitter; we're happy to offer a refuge for friendly people when that kind of thing happens. *** We also have a lot of French and German posters. *** ...and of course we encourage posting in [[Catalan]], because that's what the [[.cat]] TLD was originally created for (even if hardly anyone uses it that way anymore). ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ** '''A:''' Absolutely! We welcome all species. Especially ferrets, wombats, possums, and capybaras. But dogs are cool too. ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' ** '''A:''' See [[Toot.cat/CoC|the CoC]]. * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to help find solutions. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. *** '''Note''' that you can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be CWed. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** Note that for those who don't like using CWs, another alternative is to use hashtags -- which can be filtered against by people who don't want to see certain types of content. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. 6f53ed2aab2e1e7b2bd553472481e248e8ff875e 12 265 828 2023-07-02T19:09:26Z Woozle 1 Created page with "=Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will di..." wikitext text/x-wiki =Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will discuss each of these states in turn, so that you will be better equipped to handle whichever reality you may find yourself confronted with upon opening the box. ==Nonexistence== '''Answer 1:''' The Cat was, as of 2017, actually two cats: {{l/tc|@Pip}} and {{l/tc|@Kestra}}. They were both adopted from the same litter from an undercared-for cat in Athens, GA; both lived long and <s>happy</s> sad, pathetic, deprived lives, with Pip dying in 2019 at age 17 and Kestra surviving until 2021. Kestra is featured in Woozle's avatar. Since neither of them now exist, There Is (now) No Cat. '''Answer 2:''' The site was founded by other people (see the History section in [[Toot.cat]]) who never explained where the cat was. To this day, we still do not know. If anyone has any information, please contact [[@woozle]]. '''Answer 3:''' There should be Cat graphics instead of mastodon graphics ([[:File:Mastoglitch-1.png|1]],[[:File:Mastoglitch-2.png|2]],[[:File:Mastoglitch-3.png|3]],[[:File:Default-avatar.png|4]]). This is a woeful oversight which we hope to address before we ourselves become extinct. ==Singular Existence== '''Answer 1:''' The Cat may be found in [https://toot.cat/favicon.ico the site's favicon]. Give pets. '''Answer 2:''' The Cat is secretly Kestra in Woozle's avatar. ==Plural Existence== There are many cats and cat-identified beings here! A woefully incomplete list put together after scrolling around the local timeline for a bit (I'll try to add more later): * {{l/tc|@molsonkitty}} * {{l/tc|@solveig}} * {{l/tc|@somecat}} * {{l/tc|@yudderick}} & Co I should also do a list of accounts that are cat-related in other ways; there are quite a few. d6a874ec6e7d9847c01469082442760c2f12db1b 829 828 2023-07-02T19:15:18Z Woozle 1 /* Plural Existence */ wikitext text/x-wiki =Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will discuss each of these states in turn, so that you will be better equipped to handle whichever reality you may find yourself confronted with upon opening the box. ==Nonexistence== '''Answer 1:''' The Cat was, as of 2017, actually two cats: {{l/tc|@Pip}} and {{l/tc|@Kestra}}. They were both adopted from the same litter from an undercared-for cat in Athens, GA; both lived long and <s>happy</s> sad, pathetic, deprived lives, with Pip dying in 2019 at age 17 and Kestra surviving until 2021. Kestra is featured in Woozle's avatar. Since neither of them now exist, There Is (now) No Cat. '''Answer 2:''' The site was founded by other people (see the History section in [[Toot.cat]]) who never explained where the cat was. To this day, we still do not know. If anyone has any information, please contact [[@woozle]]. '''Answer 3:''' There should be Cat graphics instead of mastodon graphics ([[:File:Mastoglitch-1.png|1]],[[:File:Mastoglitch-2.png|2]],[[:File:Mastoglitch-3.png|3]],[[:File:Default-avatar.png|4]]). This is a woeful oversight which we hope to address before we ourselves become extinct. ==Singular Existence== '''Answer 1:''' The Cat may be found in [https://toot.cat/favicon.ico the site's favicon]. Give pets. '''Answer 2:''' The Cat is secretly Kestra in Woozle's avatar. ==Plural Existence== There are many cats and cat-identified beings here! A woefully incomplete list put together after scrolling around the local timeline for a bit (I'll try to add more later): * {{l/tc|@flippie}} * {{l/tc|@molsonkitty}} * {{l/tc|@solveig}} * {{l/tc|@somecat}} * {{l/tc|@yudderick}} & Co I should also do a list of accounts that are cat-related in other ways; there are quite a few. 614e107d53d2ff967efea3efe1063fbc0892570d 842 829 2023-07-02T19:36:24Z Woozle 1 wikitext text/x-wiki =Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will discuss each of these states in turn, so that you will be better equipped to handle whichever reality you may find yourself confronted with upon opening the box. ==Nonexistence== '''Answer 1:''' The Cat was, as of 2017, actually two cats: {{l/tc|@Pip}} and {{l/tc|@Kestra}}. They were both adopted from the same litter from an undercared-for cat in Athens, GA; both lived long and <s>happy</s> sad, pathetic, deprived lives, with Pip dying in 2019 at age 17 and Kestra surviving until 2021. Kestra is featured in Woozle's avatar. Since neither of them now exist, There Is (now) No Cat. '''Answer 2:''' The site was founded by other people (see the History section in [[Toot.cat]]) who never explained where the cat was. To this day, we still do not know. If anyone has any information, please contact [[@woozle]]. '''Answer 3:''' There should be Cat graphics instead of mastodon graphics ([[:File:Mastoglitch-1.png|1]],[[:File:Mastoglitch-2.png|2]],[[:File:Mastoglitch-3.png|3]],[[:File:Default-avatar.png|4]]). This is a woeful oversight which we hope to address before we ourselves become extinct. ==Singular Existence== '''Answer 1:''' The Cat may be found in [https://toot.cat/favicon.ico the site's favicon]. Give pets. '''Answer 2:''' The Cat is secretly Kestra in Woozle's avatar. ==Plural Existence== There are many cats and cat-identified beings here! A woefully incomplete list put together after scrolling around the local timeline for a bit (I'll try to add more later): * {{l/tc|@flippie}} * {{l/tc|@molsonkitty}} * {{l/tc|@RemyGypsy}} * {{l/tc|@solveig}} * {{l/tc|@somecat}} * {{l/tc|@yudderick}} & Co I should also do a list of accounts that are cat-related in other ways; there are quite a few. 3d5c263590e455aa380a5316bf4a61da7c89fff8 844 842 2023-07-02T19:40:52Z Woozle 1 /* Singular Existence */ wikitext text/x-wiki =Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will discuss each of these states in turn, so that you will be better equipped to handle whichever reality you may find yourself confronted with upon opening the box. ==Nonexistence== '''Answer 1:''' The Cat was, as of 2017, actually two cats: {{l/tc|@Pip}} and {{l/tc|@Kestra}}. They were both adopted from the same litter from an undercared-for cat in Athens, GA; both lived long and <s>happy</s> sad, pathetic, deprived lives, with Pip dying in 2019 at age 17 and Kestra surviving until 2021. Kestra is featured in Woozle's avatar. Since neither of them now exist, There Is (now) No Cat. '''Answer 2:''' The site was founded by other people (see the History section in [[Toot.cat]]) who never explained where the cat was. To this day, we still do not know. If anyone has any information, please contact [[@woozle]]. '''Answer 3:''' There should be Cat graphics instead of mastodon graphics ([[:File:Mastoglitch-1.png|1]],[[:File:Mastoglitch-2.png|2]],[[:File:Mastoglitch-3.png|3]],[[:File:Default-avatar.png|4]]). This is a woeful oversight which we hope to address before we ourselves become extinct. ==Singular Existence== '''Answer 1:''' The Cat may be found in [https://toot.cat/favicon.ico the site's favicon]. Give pets. '''Answer 2:''' The Cat is secretly Kestra in Woozle's avatar. '''Answer 3:''' "Cat" is a user-role which we will [https://toot.cat/@news/110646085088425956 grant on request]. ==Plural Existence== There are many cats and cat-identified beings here! A woefully incomplete list put together after scrolling around the local timeline for a bit (I'll try to add more later): * {{l/tc|@flippie}} * {{l/tc|@molsonkitty}} * {{l/tc|@RemyGypsy}} * {{l/tc|@solveig}} * {{l/tc|@somecat}} * {{l/tc|@yudderick}} & Co I should also do a list of accounts that are cat-related in other ways; there are quite a few. b6d6bd8209df15629efd9257558c612116fb3a56 848 844 2023-07-03T15:34:44Z Woozle 1 /* Singular Existence */ wikitext text/x-wiki =Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will discuss each of these states in turn, so that you will be better equipped to handle whichever reality you may find yourself confronted with upon opening the box. ==Nonexistence== '''Answer 1:''' The Cat was, as of 2017, actually two cats: {{l/tc|@Pip}} and {{l/tc|@Kestra}}. They were both adopted from the same litter from an undercared-for cat in Athens, GA; both lived long and <s>happy</s> sad, pathetic, deprived lives, with Pip dying in 2019 at age 17 and Kestra surviving until 2021. Kestra is featured in Woozle's avatar. Since neither of them now exist, There Is (now) No Cat. '''Answer 2:''' The site was founded by other people (see the History section in [[Toot.cat]]) who never explained where the cat was. To this day, we still do not know. If anyone has any information, please contact [[@woozle]]. '''Answer 3:''' There should be Cat graphics instead of mastodon graphics ([[:File:Mastoglitch-1.png|1]],[[:File:Mastoglitch-2.png|2]],[[:File:Mastoglitch-3.png|3]],[[:File:Default-avatar.png|4]]). This is a woeful oversight which we hope to address before we ourselves become extinct. ==Singular Existence== '''Answer 1:''' The Cat may be found in [https://toot.cat/favicon.ico the site's favicon]. Give pets. '''Answer 2:''' The Cat is secretly Kestra in Woozle's avatar. '''Answer 3:''' "Cat" is a user-role which we will [https://toot.cat/@news/110646085088425956 grant on request]. '''Answer 4:''' The Toot Cat is over there [points at right side of page]. ==Plural Existence== There are many cats and cat-identified beings here! A woefully incomplete list put together after scrolling around the local timeline for a bit (I'll try to add more later): * {{l/tc|@flippie}} * {{l/tc|@molsonkitty}} * {{l/tc|@RemyGypsy}} * {{l/tc|@solveig}} * {{l/tc|@somecat}} * {{l/tc|@yudderick}} & Co I should also do a list of accounts that are cat-related in other ways; there are quite a few. 86af00b35b6a20832dacdd817a9e5ff30c4bc4e6 849 848 2023-07-03T15:35:42Z Woozle 1 wikitext text/x-wiki [[File:The Toot Cat.3161a5d9e683251f.jpg|thumb|This image appeared in fedi sometime in early 2023, I think; trying to find out who made it...]] =Where's the Cat?= This question is often asked; there is no one right answer. The Cat remains in a quantum state in between nonexistence, existence, and plurality. We will discuss each of these states in turn, so that you will be better equipped to handle whichever reality you may find yourself confronted with upon opening the box. ==Nonexistence== '''Answer 1:''' The Cat was, as of 2017, actually two cats: {{l/tc|@Pip}} and {{l/tc|@Kestra}}. They were both adopted from the same litter from an undercared-for cat in Athens, GA; both lived long and <s>happy</s> sad, pathetic, deprived lives, with Pip dying in 2019 at age 17 and Kestra surviving until 2021. Kestra is featured in Woozle's avatar. Since neither of them now exist, There Is (now) No Cat. '''Answer 2:''' The site was founded by other people (see the History section in [[Toot.cat]]) who never explained where the cat was. To this day, we still do not know. If anyone has any information, please contact [[@woozle]]. '''Answer 3:''' There should be Cat graphics instead of mastodon graphics ([[:File:Mastoglitch-1.png|1]],[[:File:Mastoglitch-2.png|2]],[[:File:Mastoglitch-3.png|3]],[[:File:Default-avatar.png|4]]). This is a woeful oversight which we hope to address before we ourselves become extinct. ==Singular Existence== '''Answer 1:''' The Cat may be found in [https://toot.cat/favicon.ico the site's favicon]. Give pets. '''Answer 2:''' The Cat is secretly Kestra in Woozle's avatar. '''Answer 3:''' "Cat" is a user-role which we will [https://toot.cat/@news/110646085088425956 grant on request]. '''Answer 4:''' The Toot Cat is over there [points at right side of page]. ==Plural Existence== There are many cats and cat-identified beings here! A woefully incomplete list put together after scrolling around the local timeline for a bit (I'll try to add more later): * {{l/tc|@flippie}} * {{l/tc|@molsonkitty}} * {{l/tc|@RemyGypsy}} * {{l/tc|@solveig}} * {{l/tc|@somecat}} * {{l/tc|@yudderick}} & Co I should also do a list of accounts that are cat-related in other ways; there are quite a few. 15a2ea5eb7299bc6258b01ec87db45cdba09efe6 0 16 830 388 2023-07-02T19:19:49Z Woozle 1 Woozle moved page [[Woozle]] to [[@Woozle]]: decided it should work this way wikitext text/x-wiki I've been sysop of {{l/pub|toot.cat}} since the beginning of 2018, having volunteered to take the reins from @polymerwitch when she found herself overcommitted. There's probably more than you could possibly ever want to know about me on {{ls/domain|woozalia.com}}. Also, have some photos of The {{l/pub|TootCave}}. ==Bloggish== * {{ld/blog|2018-04-05|justice in the fediverse}} * {{ld/blog|2018-04-07|sketching a code}} ==Pages== * {{l/sub|GlitchSoc}}: feature requests * {{l/sub|malusers}} 035507fda19b47662f66b5f3bbdfe4ebab41b307 0 266 831 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle]] to [[@Woozle]]: decided it should work this way wikitext text/x-wiki #REDIRECT [[@Woozle]] 87f3cb2e18c16e5e8c90312c49ccb54cf51c0a43 0 22 832 390 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/2018/04/05/justice in the fediverse]] to [[@Woozle/2018/04/05/justice in the fediverse]]: decided it should work this way wikitext text/x-wiki {{box/principles| : I strive to evaluate first in terms of potential harm. : I strive not to decide until I have all the facts. }} I'm working towards a redesigned process of justice. What I've come up with isn't as radically revisioned as what I'd like to do in the long run, but I don't have the tools for that yet. Traditional justice systems are usually based on hierarchies &ndash; something that has harmed many of us and which I believe most of us want to move away from. Justice should empower us all equally. Ideally, a system of justice would rely more on rallying our common sense of empathy<ref name=sydney /> to create the authority necessary to exercise power against malicious acts. To do that, we need tools that let us nurture and empower empathy, and disempower selfishness. We're not there yet. What we do have now is: * a fediverse, with a very simple and fairly short hierarchy: instance admins on the upper layer and regular users on the lower, with relatively minor and variable differences in power on each level, and * this wiki, in which I hope we can build a copyable navigation aid for uncertain waters &ndash; a reference index, a catalog of findable landmarks. It has fallen naturally to the instance admins to administer justice &ndash; and yet we barely have the seeds of a set of best practices. We've done well crafting our Codes of Conduct to define the responsibilities of our users &ndash; but recent events have shown that we need Codes of Justice, to define (and limit) the responsibilities of our admins. Power must be accountable, and must be earned through its use in the service of the disempowered<ref name=banazi /> or else it is illegitimate. A Code of Justice needs to be able to answer certain questions: * As a user, how can I seek redress for harm done to me? * As an admin &mdash; ** under what circumstances am I enabled to act? ** under what circumstances do I have some moral obligation to act? ** what are the limits of the actions I may take? There are many different reasonable answers to these questions; I'm going to try to set out some for me to follow as admin of toot.cat. ==Footnotes== <references> <ref name=sydney>Apparently I now have a Sydney head-squirrel because I'm hearing strenuous objections to the idea that we could ever rely on any such thing, especially not now, and she's really quite skeptical that such a thing really exists in the first place, so the idea of depending on it for our safety is really kind of hecking scary. I'm... not ignoring her, but deferring that discussion for a later time; my statement was speculative and I agree we're not ready to go there yet.</ref> <ref name=banazi>This is essentially why we penalize instances that enable right-wing propaganda: they are failing in their service to the disempowered. They fail to protect the weak from the strength of induced collective hostility.</ref> </references> 11ccbe1756e47d9e535bd3675d618d74636006d3 0 267 833 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/2018/04/05/justice in the fediverse]] to [[@Woozle/2018/04/05/justice in the fediverse]]: decided it should work this way wikitext text/x-wiki #REDIRECT [[@Woozle/2018/04/05/justice in the fediverse]] b17ed11fbb220214be065299ea58858d1b7df224 0 24 834 392 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/2018/04/07/sketching a code]] to [[@Woozle/2018/04/07/sketching a code]]: decided it should work this way wikitext text/x-wiki {{box/principles| : Words have consequences. : All accusations should be taken seriously. : No accusation should be accepted as truth unless the evidence supports it. : Both accusers and accused may need some protection. : A lie often contains just enough truth to make it plausible. }} ==Public Intervention Process<ref name=pip />== Other instances may adopt this, modify it, or ignore it completely; I'm content to let the marketplace of kindness<ref name=note1 /> decide whether such a thing is necessary or not, and to let the process of considered discussion refine it as needed &ndash; but tentatively, here's the way I think it should work for toot.cat. '''If you have a grievance against another user'''<ref name=note2 /> and would like me (as sysop of this instance) to do something about it: # "@" me (@woozle@toot.cat) with a public<ref name=public /> toot stating the nature of the problem and that you are requesting an Intervention. #* The primary types of problem I expect to be addressing are: (a) someone has abused you, or (b) someone has falsely accused you of abuse &ndash; but others may emerge. # This means I have your permission to investigate the situation and publicly post my findings on Mew (this wiki). #* I will probably need to ask a lot of nosy questions, both to you and the other parties involved. Let me know if you anticipate any problems with this. #* These discussions should take place on Mastodon<ref name=mastodm /> so as to be part of the public record, though I can make exceptions if there's a good reason. # Once I have investigated sufficiently to satisfy ''my'' standards of evidence, I will post a preliminary determination for public feedback. # Anyone may state objections to this conclusion at any time, and I will either answer them or reconsider my conclusion, possibly re-opening the investigation. # Anyone may choose to go on record as supporting or opposing the conclusion. I will make these part of the public record to the best of my ability. #* Please note that opposition is not the same as stating an objection. I won't reconsider just because you oppose; you need to make an argument for why it is wrong. Please note that this is a good-faith process &ndash; i.e. one that depends on all participants being honest about their beliefs and intentions &ndash; and I will deal firmly with anyone I find to be acting otherwise. I have over a decade of experience spotting manipulation and evasion in online arguments. ==Footnotes== <references> <ref name=note1>This is a reference to the semi-capitalistic "marketplace of ideas" concept, with an ironic twist since capitalists don't seem to place much (if any) value on kindness (so their marketplaces tend to squash it out of existence) and since most Mastodonians are staunchly anti-marketist. That said, the idea of having numerous instances among which users may freely choose to invest various amounts of their time and energy actually ''is'' a kind of marketplace that's totally compatible with anarcho-capitalism &ndash; except I think we'd all tend to agree that basically having one person who gets to decide pretty much everything about how the system works is kind of iffy.</ref> <ref name=note2>This applies whether or not either user is on toot.cat, though obviously my actions will be more effective if one or the other is.</ref> <ref name=public>You could also approach me privately (DM or whatever) to discuss it before stating it publicly, or you might need me to try to keep your name out of the public process. I'm willing to consider intervening less publicly, but I suspect it will severely limit any good I might be able to do; if this emerges as a frequent need, I'll probably need to write up a separate process for dealing with it.</ref> <ref name=pip>It seems entirely appropriate that this abbreviates to PIP, which is also the name of our very messed-up cat ([https://toot.cat/@Pip Mastodon], [https://wiki.hypertwins.org/Pip HypertWiki]), since it is only invoked when a situation has become very messed-up. It is my hope that this process will soon become informally known as "requesting a Pip".</ref> <ref name=mastodm>Tentatively, this should be public but "unlisted" or "followers only". I may need to set up a dedicated investigation account so people can decide whether they want the investigation in their streams or not.</ref> </references> 1370855f907cd19de4fed13fbf87772cd350b54f 0 268 835 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/2018/04/07/sketching a code]] to [[@Woozle/2018/04/07/sketching a code]]: decided it should work this way wikitext text/x-wiki #REDIRECT [[@Woozle/2018/04/07/sketching a code]] 7064b58e7f948de520f10d27df78cfc4faac442b 0 61 836 394 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/GlitchSoc]] to [[@Woozle/GlitchSoc]]: decided it should work this way wikitext text/x-wiki ==Feature Requests== ===moderation panel=== * option to save a note when taking an action (right now, can only do these one at a time) * option to message the reporting user as part of the moderation action * should be a link to the problem user's stream * (large) retain deleted information somewhere, preferably in reinstateable form (don't destroy the evidence!) ===admin options=== * option for admins to get notifs (in web UI, not just email) of reports * option for admins to get notifs of new signups * somehow streamline the process so that multiple accounts can be silenced ** maybe a list, in admin, of accounts by signup date, with easy links to moderation panel *** preferably also a way to make notes on each user, visible only to other admins 3d7a5162c27bff1ed0a8f6158cbb54b7639f69cc 0 269 837 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/GlitchSoc]] to [[@Woozle/GlitchSoc]]: decided it should work this way wikitext text/x-wiki #REDIRECT [[@Woozle/GlitchSoc]] 1e4a42862c74b9b662a92617a4663510f81b8d63 0 44 838 784 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/malusers]] to [[@Woozle/malusers]]: decided it should work this way wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://lor.sh/@dump_stack dump_stack] | {{ls/domain|lor.sh}} | Mastodon | * '''2020-02-24''' [https://lor.sh/@dump_stack/103715838645490658] "people have anti-homeless attitudes because most of the time being homeless is a choice not a matter of chance." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |- | [https://zirk.us/@dambaras dambaras] ([https://chass.ncsu.edu/people/dambaras/ David Ambaras]) | {{ls/domain|zirk.us}} | Mastodon | * '''2023-04-06''' [https://web.archive.org/web/20230406141102/https://zirk.us/@dambaras/110149627484335327 response]: replying to my post with insult, and never backing down |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li. '''Update 2018-10-07''': They have now been blocked after a report from a known user.</ref> </references> d8785aa42fecc984d631f35e7c370951a4342db0 0 270 839 2023-07-02T19:19:50Z Woozle 1 Woozle moved page [[Woozle/malusers]] to [[@Woozle/malusers]]: decided it should work this way wikitext text/x-wiki #REDIRECT [[@Woozle/malusers]] f0ba5119f216113b6d34ffd847bc8dd80dc975ad 0 271 840 2023-07-02T19:20:27Z Woozle 1 Redirected page to [[@Woozle]] wikitext text/x-wiki #redirect [[@Woozle]] fe6d8c4876368e2e245c43d8a8ecbfebea5a5306 12 272 841 2023-07-02T19:30:53Z Woozle 1 Created page with "==OOO== The original/obvious/official uses of CWs were: * to warn about content some people find unpleasant, so they don't have to see it * to hide spoilers Other uses includ..." wikitext text/x-wiki ==OOO== The original/obvious/official uses of CWs were: * to warn about content some people find unpleasant, so they don't have to see it * to hide spoilers Other uses include: * a title or subject-line * the setup to a joke (the punchline goes in the body) * the tagline for an in-joke -- examples include: ** "in this house..." posts<ref name=note1 /> ** "it's been..." posts<ref name=note1 /> ==Footnote== <references> <ref name=note1>These in particular were more popular in the early days of Mastodon, 2017-ish.</ref> </references> d4b0706d23ca60d4038abe95965a7aceeb5e61ea 6 273 847 2023-07-03T15:33:08Z Woozle 1 I'm trying to find out who created this image, as I'd love to use it more extensively. wikitext text/x-wiki == Summary == I'm trying to find out who created this image, as I'd love to use it more extensively. dd9c75fbea4a08dc1630cbc7d6c6c16f03108155 0 56 851 362 2023-07-04T17:21:45Z Woozle 1 wikitext text/x-wiki In order to comply with the spirit of the [[.cat]] TLD ToS (even if it's no longer being enforced at all and hasn't been for years), we do encourage posting in Catalan. ==Notes== some cover songs possibly in Catalan (hey, it's all I've been able to find so far!): * [https://www.youtube.com/watch?v=Bw6Q9GiVaYw Mr Tambourine Man - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=t17tD0ByhR4 500 Millas - Todo Tiene Su Sitio Bajo El Cielo - Txarango [official audio]] * [https://www.youtube.com/watch?v=GFav2hjkLjE 12. Arriba la nit - Txarango] * [https://www.youtube.com/watch?v=e2pEx7PAb30 Txarango - Agafant l'horitzó (ft. G. Humet, Aspencat, C. Freixas, Les Kol·lontai i Ascensa Furore)] ==Reference== * [[wikipedia:Catalan language|Wikipedia]] 7698460b3e93f766655d78ca92fd76046efe50f6 0 274 853 2023-07-06T15:03:45Z Woozle 1 Created page with "Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account. * Meta has said that yes, they will be mining Threads user dat..." wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account. * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) c1b2a22a31aa9b619ebe14a512c498793d4e734e 860 853 2023-07-06T20:44:47Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account. * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. 87c9305dd6e8fc8141d33b0d8e049f8037db53f4 861 860 2023-07-06T21:11:32Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> 1086c5a16f8b91528ea6f5788c5f6a0a0675299d 862 861 2023-07-07T01:12:58Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * "Liberals of TikTok" (a group which promotes right-wing views by straw-manning the center-left) has not been banned, which suggests other right-wing groups will be (or already are) welcome. ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> cdca66b7de53061c3a0044782ecbfe05d9901ab9 863 862 2023-07-07T12:41:05Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** "Liberals of TikTok" (a group which promotes right-wing views by straw-manning the center-left) has not been banned. ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> 7a3cc1811a5549858d2013424dfa58e606790f6a 864 863 2023-07-07T12:54:29Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ groups which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] Observers have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; I remember that name but can't quickly find confirmation of how he is problematic. ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> 26861045d7030ac7dd4725bffec67753b0cdd93f 865 864 2023-07-07T12:54:54Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ groups which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; I remember that name but can't quickly find confirmation of how he is problematic. ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> 2789e6248ec6711dd450781553ad2c1dd58ac779 10 275 854 2023-07-06T15:36:23Z Woozle 1 Created page with "[[wiktionary:{{{1}}}|{{{1}}}]]" wikitext text/x-wiki [[wiktionary:{{{1}}}|{{{1}}}]] f9988a57c371d8d7aced0cd770d11801b817ef4e 0 276 855 2023-07-06T15:47:13Z Woozle 1 Created page with "[[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by Meta (formerly Facebook, Inc.) in July 2023. I had already decided, as of May o..." wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by Meta (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 217e9a44f7135032123deb1bacb456de13554f3c 856 855 2023-07-06T15:49:22Z Woozle 1 /* Terms under which I'd reconsider */ wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by Meta (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 1d3ded64321cdf8ea1b3e41adae46da6cd38ca98 857 856 2023-07-06T16:11:18Z Woozle 1 /* Terms under which I'd reconsider */ wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by Meta (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> c44c04363eba70be1b2e9f76bcd186ee9b893c2a 858 857 2023-07-06T16:13:25Z Woozle 1 wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by Meta (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> e150adc81fe6a509a22f89409c839e5daf08ed42 859 858 2023-07-06T16:41:46Z Woozle 1 wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 13d6938467e99d6dc19ef6a225e30823f857263d 0 277 866 2023-07-07T13:40:00Z Woozle 1 Created page with "{{fmt/title|Embrace, Extend, Extinguish|...or is that "Exterminate"?}} '''Embrace, Extend, Extinguish''' is a strategy used by large tech companies to sabotage community-owned..." wikitext text/x-wiki {{fmt/title|Embrace, Extend, Extinguish|...or is that "Exterminate"?}} '''Embrace, Extend, Extinguish''' is a strategy used by large tech companies to sabotage community-owned technology, which they rightly see as a threat to their ability to control users and dominate resources. The earliest known use of this concept &ndash; described using the inaccurate term "innovate" instead of "extinguish" &ndash; is in a 1994 Microsoft (MS) memo regarding efforts to destroy the dominance of Netscape's web browser by "embracing" the web with Microsoft Internet Explorer (MSIE), "extending" web standards using technology that nobody else could support or keep up with, and thereby positioning MSIE as the "leading" browser defining the latest standards that all others had to copy in order to be fully compatible. MS had previously tried this strategy in hardware when they tried to recapture control of the Personal Computer standard by replacing the then-industry-standard ISA card format with their own proprietary "microchannel" standard. This, fortunately, failed, and ISA was able to continue evolving (through EISA, PCI, etc.) into the standards we use today. The battlefield in software, especially with regard to federated protocols, is unfortunately much more vulnerable to this technique: * In 2011, Google+ was able to capture the increasing interest in social networks and thereby divert resources and attention away from Diaspora, the first-ever federated social network. * Social media companies at first embraced XMPP (an open federated protocol for realtime chat) in the form of GTalk and Facebook Messenger, then later disabled federation after many XMPP users had abandoned open-source XMPP clients for the seemingly-friendlier interfaces offered by Google and Facebook. XMPP still exists, but is a ghost of its former self and an even larger ghost of what it could have been. * RSS feeds, which once dominated social media, were effectively killed off by Google's termination of Google Reader. RSS still exists, but is again a shadow of what it was even before Reader. * Email is currently under siege, as both Google (Gmail) and especially Microsoft (Outlook) increasingly block or auto-spam messages from independently-operated email servers. ** '''Anecdote''': I have not been able to send email to outlook.com addresses for a decade or more. For several years, I thought my auldest friend was ghosting me, as I never got back any bounce messages (which is what servers are ''supposed'' to do when they reject an incoming message); it was only when I enabled "Delivery status notification" (something that is not supported by many email clients) that I was able to determine that Outlook was in fact silently rejecting them. Further research found that MS does not offer any clear explanation of why they are doing this, much less how to get greenlisted so they will stop. --[[Woozle]] While we don't yet know whether [[Meta Threads]] or [[BlueSky]] intend to pursue this strategy, it is easy enough to imagine how to apply any or all of the above techniques to the ActivityPub protocol and fediverse &ndash; and there is absolutely no reason to think that doing so ''isn't'' among their plans. 1dae1dafd8aa58936f9dc70d28fd772f813cf258 10 278 867 2023-07-07T13:41:40Z Woozle 1 Created page with "{{l/wp|{{{1}}}|Wikipedia}}" wikitext text/x-wiki {{l/wp|{{{1}}}|Wikipedia}} 378889ec19bd4c0a2a91eb3ac84e956cec4bc020 0 277 868 866 2023-07-07T13:41:49Z Woozle 1 wikitext text/x-wiki {{fmt/title|Embrace, Extend, Extinguish|...or is that "Exterminate"?}} '''Embrace, Extend, Extinguish''' is a strategy used by large tech companies to sabotage community-owned technology, which they rightly see as a threat to their ability to control users and dominate resources. The earliest known use of this concept &ndash; described using the inaccurate term "innovate" instead of "extinguish" &ndash; is in a 1994 Microsoft (MS) memo regarding efforts to destroy the dominance of Netscape's web browser by "embracing" the web with Microsoft Internet Explorer (MSIE), "extending" web standards using technology that nobody else could support or keep up with, and thereby positioning MSIE as the "leading" browser defining the latest standards that all others had to copy in order to be fully compatible. MS had previously tried this strategy in hardware when they tried to recapture control of the Personal Computer standard by replacing the then-industry-standard ISA card format with their own proprietary "microchannel" standard. This, fortunately, failed, and ISA was able to continue evolving (through EISA, PCI, etc.) into the standards we use today. The battlefield in software, especially with regard to federated protocols, is unfortunately much more vulnerable to this technique: * In 2011, Google+ was able to capture the increasing interest in social networks and thereby divert resources and attention away from Diaspora, the first-ever federated social network. * Social media companies at first embraced XMPP (an open federated protocol for realtime chat) in the form of GTalk and Facebook Messenger, then later disabled federation after many XMPP users had abandoned open-source XMPP clients for the seemingly-friendlier interfaces offered by Google and Facebook. XMPP still exists, but is a ghost of its former self and an even larger ghost of what it could have been. * RSS feeds, which once dominated social media, were effectively killed off by Google's termination of Google Reader. RSS still exists, but is again a shadow of what it was even before Reader. * Email is currently under siege, as both Google (Gmail) and especially Microsoft (Outlook) increasingly block or auto-spam messages from independently-operated email servers. ** '''Anecdote''': I have not been able to send email to outlook.com addresses for a decade or more. For several years, I thought my auldest friend was ghosting me, as I never got back any bounce messages (which is what servers are ''supposed'' to do when they reject an incoming message); it was only when I enabled "Delivery status notification" (something that is not supported by many email clients) that I was able to determine that Outlook was in fact silently rejecting them. Further research found that MS does not offer any clear explanation of why they are doing this, much less how to get greenlisted so they will stop. --[[Woozle]] While we don't yet know whether [[Meta Threads]] or [[BlueSky]] intend to pursue this strategy, it is easy enough to imagine how to apply any or all of the above techniques to the ActivityPub protocol and fediverse &ndash; and there is absolutely no reason to think that doing so ''isn't'' among their plans. ==Reference== * {{l/wp/ref|Embrace, extend, and extinguish}} 47b23c56d839a66332962f593c9f5e0271ebaaa4 0 276 869 859 2023-07-07T13:45:01Z Woozle 1 wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? (more: [[EEE]]) Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 72a9747912c680f029d25274efa4838cb69f8d11 870 869 2023-07-07T13:45:52Z Woozle 1 wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? (more: [[EEE]]) Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. (The same conditions should probably also apply to [[BlueSky]]; I'll eventually do a page about that when I have more information. -W.) ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 6f49607414cfd8930e6b1f342bb38931333d56a4 884 870 2023-07-08T17:09:53Z Woozle 1 /* Why are we blocking them? */ wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== [[File:Shuttering google reader.334841466545c250.jpeg|thumb|Google EEEd RSS feeds]] The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already {{l/sub|issues}} with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? (more: [[EEE]]) Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. (The same conditions should probably also apply to [[BlueSky]]; I'll eventually do a page about that when I have more information. -W.) ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 9a7d0e092b87da7f91fa6aa6bc45e854df601425 885 884 2023-07-08T21:14:25Z Woozle 1 /* Too Much Damn Power */ wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== [[File:Shuttering google reader.334841466545c250.jpeg|thumb|Google EEEd RSS feeds]] The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already '''{{l/sub|issues}}''' with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body. Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person. Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? (more: [[EEE]]) Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. (The same conditions should probably also apply to [[BlueSky]]; I'll eventually do a page about that when I have more information. -W.) ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> 8cbb56f97899f8bb145f3c1ab2de9ff9d7a254d8 0 274 871 865 2023-07-07T13:49:40Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; I remember that name but can't quickly find confirmation of how he is problematic. ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> 494fbbc9148180d4d4a3bf806d641abd51291d2e 875 871 2023-07-07T15:16:01Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; I remember that name but can't quickly find confirmation of how he is problematic. Some preliminary links: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> 9e21c8580e2a0ce477cc73b1f4ba4f70473a9f39 877 875 2023-07-07T20:00:44Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues. [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/] ([https://yatil.social/@yatil/110673817235133663 h/t]) Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; I remember that name but can't quickly find confirmation of how he is problematic. Some preliminary links: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> d2684edeca5cd3068920505e10e7cb055d72b389 878 877 2023-07-07T23:06:34Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues. [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/] ([https://yatil.social/@yatil/110673817235133663 h/t]) ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; I remember that name but can't quickly find confirmation of how he is problematic. Some preliminary links: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> fb96d083815a7199231a6b0b3461c95681b27c97 879 878 2023-07-07T23:11:26Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues. [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/] ([https://yatil.social/@yatil/110673817235133663 h/t]) ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; There's more information about him here: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnote== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> </references> eb140c12abba3d9ef409fc8530562576496f3773 880 879 2023-07-07T23:14:06Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues.<ref name=linkedin1 /> ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; There's more information about him here: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnotes== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> <ref name=linkedin1>'''2023-07-07''' [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/ Yesterday I had a post go viral, today I'm banned.] ([https://yatil.social/@yatil/110673817235133663 h/t])</ref> </references> e08690163c41205a42cf66ed47add647e07420b8 881 880 2023-07-08T00:29:31Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues.<ref name=linkedin1 /> ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) * They have actively helped law enforcement to go after people legally seeking abortions by traveling to other states. [https://hachyderm.io/@crowgirl/110672760812400852] Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; There's more information about him here: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnotes== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> <ref name=linkedin1>'''2023-07-07''' [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/ Yesterday I had a post go viral, today I'm banned.] ([https://yatil.social/@yatil/110673817235133663 h/t])</ref> </references> 46b8b36a80d54a7a32b9c10d7a2d477f08462c72 886 881 2023-07-08T21:16:59Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues.<ref name=linkedin1 /> ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) * They have actively helped law enforcement to go after people legally seeking abortions by traveling to other states. [https://hachyderm.io/@crowgirl/110672760812400852] * They ''were'' flagging disinfo-spreading accounts, but the disinfo-spreading accounts didn't like having it pointed out that they spread disinfo, so the flagging has been discontinued. ** '''2023-07-07''' [https://mashable.com/article/threads-false-information-label-donald-trump-jr-error Threads backtracks flagging right-wing users for spreading disinformation] Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; There's more information about him here: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnotes== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> <ref name=linkedin1>'''2023-07-07''' [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/ Yesterday I had a post go viral, today I'm banned.] ([https://yatil.social/@yatil/110673817235133663 h/t])</ref> </references> f2d85dfa5d5fe9893393b4d38c5822ecfd487bd6 887 886 2023-07-09T00:04:47Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues.<ref name=linkedin1 /> ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) * They have actively helped law enforcement to go after people legally seeking abortions by traveling to other states. [https://hachyderm.io/@crowgirl/110672760812400852] * They ''were'' flagging disinfo-spreading accounts, but the disinfo-spreading accounts didn't like having it pointed out that they spread disinfo, so the flagging has been discontinued. ** '''2023-07-07''' [https://mashable.com/article/threads-false-information-label-donald-trump-jr-error Threads backtracks flagging right-wing users for spreading disinformation] * Threads is, unsurprisingly, very popular with the fash: ** '''2023-07-07''' [https://www.mediamatters.org/facebook/far-right-figures-including-nazi-supporters-anti-gay-extremists-and-white-supremacists-are Far-right figures, including Nazi supporters, anti-gay extremists, and white supremacists, are flocking to Threads] Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; There's more information about him here: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnotes== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> <ref name=linkedin1>'''2023-07-07''' [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/ Yesterday I had a post go viral, today I'm banned.] ([https://yatil.social/@yatil/110673817235133663 h/t])</ref> </references> e8def07ac48fabe51667636f76a8a56733eda786 888 887 2023-07-09T13:01:47Z Woozle 1 wikitext text/x-wiki Known ethical problems with MT: * You can't delete your Threads account without deleting your Instagram account.<ref name=note1 /> * Meta has said that yes, they will be mining Threads user data as they do everywhere else. (Why wouldn't they?) ** '''2023-07-08''' [https://arstechnica.com/security/2023/07/how-threads-privacy-policy-compares-to-twitters-and-its-rivals/ How Threads' privacy policy compares to Twitter's (and its rivals')] ([https://universeodon.com/@JenLucPiquant/110684029466181801 h/t]) * They seem to be systematically [https://xantronix.social/@megaspel/110666980545804656 doxxing their users]. * They seem to be entirely tolerant of intolerance: ** Threads [https://blahaj.zone/notes/9gvlqxpm5s apparently considers it okay] to call LGBTQ+ people "groomers". ** Anti-LGBTQ+ accounts which Threads is allowing include: *** "Libs of TikTok", a group which promotes right-wing views by straw-manning the center-left *** "Gays Against Groomers" [https://artisan.chat/@silverseams/110667684777788597] *** PragerU (Dennis Prager; see [https://rationalwiki.org/wiki/Dennis_Prager RationalWiki]) * There are apparently issues with accessibility, and deep-seated denial of those issues.<ref name=linkedin1 /> ** Apparently there is no way to add descriptions to images. (There are presumably other issues; this is just the one I currently know about.) * They have actively helped law enforcement to go after people legally seeking abortions by traveling to other states. [https://hachyderm.io/@crowgirl/110672760812400852] * They ''were'' flagging disinfo-spreading accounts, but the disinfo-spreading accounts didn't like having it pointed out that they spread disinfo, so the flagging has been discontinued. ** '''2023-07-07''' [https://mashable.com/article/threads-false-information-label-donald-trump-jr-error Threads backtracks flagging right-wing users for spreading disinformation] * Threads is, unsurprisingly, very popular with the fash: ** '''2023-07-07''' [https://www.mediamatters.org/facebook/far-right-figures-including-nazi-supporters-anti-gay-extremists-and-white-supremacists-are Far-right figures, including Nazi supporters, anti-gay extremists, and white supremacists, are flocking to Threads] Observers [https://social.pixie.town/@joepie91/110668293064374435] have also spotted Gary Vaynerchuk (GaryVee), noted grifter, talking directly with Zuckerberg; There's more information about him here: * '''2022-06-22''' [https://www.youtube.com/watch?v=4y0nR0E8pk4 Connecting the Manosphere] (video, 1:49:44, FD Signifier) (I have not watched this) * '''2022-04-06''' [https://www.youtube.com/watch?v=OVE8J8dwJ5E How GaryVee manipulates you.] (video, 1:19:48, ThoughtSlime): recommended * '''2016-06-22''' [https://www.mic.com/articles/146809/gary-vaynerchuk-apologizes-for-outrageously-sexist-party-invitation Gary Vaynerchuk Apologizes For Outrageously Sexist Party Invitation] ==Footnotes== <references> <ref name=note1>'''2023-07-06''' [https://www.vice.com/en/article/bvjvb5/threads-instagram-trap-shows-why-facebook-should-have-been-broken-up-years-ago Threads' Instagram 'Trap' Shows Why Facebook Should Have Been Broken Up Years Ago] ([https://universeodon.com/@JenLucPiquant/110668721284327276 h/t])</ref> <ref name=linkedin1>'''2023-07-07''' [https://www.linkedin.com/posts/kelsey-lindell-265a26184_yesterday-i-had-a-post-go-viral-today-im-activity-7083100287179108352-3IJb/ Yesterday I had a post go viral, today I'm banned.] ([https://yatil.social/@yatil/110673817235133663 h/t])</ref> </references> 40dbe583b6d694cdbe2ae4fec76e613172f0daf2 12 254 872 807 2023-07-07T14:22:05Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== <syntaxhighlight lang=html> Character formatting: <b>bold</b> <i>italic</i> <u>underline</u> ^superscript -- e.g.: E=MC² _subscript -- e.g.: H₂O Lists: <ul><li>item one<li>item two</ul> <ol<li>item one<li>item two</ol> Links: <a href="URL">display text</a> #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link #<a href="https://toot.cat/@woozle/tagged/softwareGripe</a>softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> 43cceec37a9eae5d292d905f9f5c6eb62f652587 873 872 2023-07-07T14:27:55Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== <syntaxhighlight lang=html> <h2>Character formatting</h2> * <b>bold</b> * <i>italic</i> * <u>underline</u> * ^superscript -- e.g.: E=MC² * _subscript -- e.g.: H₂O <h2>Lists</h2> <ul><li>item one<li>item two</ul> <ol><li>item one<li>item two</ol> <h2>Links</h2> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe"</a>softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> 06e4caee76f19cc5711b0e9da8c0d80611734ec7 874 873 2023-07-07T14:34:43Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== I've posted these examples [https://toot.cat/@woozle/110673249809945566 on TootCat] so you can see how they look in practice. <syntaxhighlight lang=html> <h2>Character formatting</h2> * <b>bold</b> * <i>italic</i> * <u>underline</u> * ^superscript -- e.g.: E=MC² * _subscript -- e.g.: H₂O <h2>Lists</h2> <ul><li>item one<li>item two</ul> <ol><li>item one<li>item two</ol> <h2>Links</h2> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe"</a>softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> ea5877f5dc94d6659ea81d94fcd3b0256011283f 889 874 2023-07-12T13:43:22Z Woozle 1 fixed minor HTML error wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== I've posted these examples [https://toot.cat/@woozle/110673249809945566 on TootCat] so you can see how they look in practice. <syntaxhighlight lang=html> <h2>Character formatting</h2> * <b>bold</b> * <i>italic</i> * <u>underline</u> * ^superscript -- e.g.: E=MC² * _subscript -- e.g.: H₂O <h2>Lists</h2> <ul><li>item one<li>item two</ul> <ol><li>item one<li>item two</ol> <h2>Links</h2> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> 9f04c9ccd8eb925dfec497517216782894a499f2 895 889 2023-07-22T18:55:36Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with HTML}} Note that the "Markdown" formatting option supports all of the tags supported by the HTML option (i.e. it's a superset), and Markdown supports some things that HTML does not -- so we recommend using the Markdown option rather than HTML only. The following applies to both the HTML and Markdown options; see {{l/sub|Markdown}} for syntax that only works in the Markdown option. ==Tags== I've posted these examples [https://toot.cat/@woozle/110673249809945566 on TootCat] so you can see how they look in practice. <syntaxhighlight lang=html> <h2>Character formatting</h2> * <b>bold</b> * <i>italic</i> * <u>underline</u> * ^superscript -- e.g.: E=MC² * _subscript -- e.g.: H₂O <h2>Lists</h2> <ul><li>item one<li>item two</ul> <ol><li>item one<li>item two</ol> <h2>Links</h2> * <a href="https://mew.toot.cat/mw/Help:TootCat/HTML/formatting">MeW page about HTML formatting</a> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user NOT SUPPORTED: <pre>, <tt>, <s> </syntaxhighlight> 549f9722f47671f06bc230b68e7ef6eaafefe698 12 255 876 806 2023-07-07T15:44:08Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with Markdown}} Remember that anything that works with the [[../|HTML option]] will also work with the Markdown option! I've also posted these examples [https://toot.cat/@woozle/110673322263974593 on TootCat] so you can see how they look in practice. <syntaxhighlight lang=md> Character formatting: ===================== * **bold** * *italic* * ~~strike~~ * _underline_ * `[link text](URL)` e.g. [toot.cat](https://toot.cat) - URL must include protocol:// * ^superscript -- like: E=MC^2 * I don't know how to turn it off without a space. * You can even do supersuperscript: Normal^super^hyper makes "hyper" look like a superscript on "super" -- both higher and smaller Lists: ====== * bullet item one * bullet item two * sub-item for item 2 (2 spaces per indent) * bullet item three 1. numbered list item 1 2. numbered list item 2 Fixed-pitch: ============ `inline fixed-pitch text` ``` multiline fixed-pitch text: multiple lines of fixed-pitch font (for pasting code examples and such) ``` Syntax highlighting does not seem to be supported at present. (Tsk tsk.) Text blocks: ============ # Header 1 ## Header 2 ### Header 3 > quote-indented text Be sure to leave a blank line after the last bit of indented text, or the renderer may decide it should also be indented. (Nobody knows why.) </syntaxhighlight> ==Further Reading on Markdown== Note that TootCat only supports a small ''subset'' of Markdown. * [[wikipedia:Markdown|Wikipedia]] * [https://daringfireball.net/projects/markdown/ official site] * [https://www.markdownguide.org/ Markdown Guide] 18fb62546dfae51b0e7cae87b8ba80d512c04e70 6 279 882 2023-07-08T17:08:19Z Woozle 1 * '''description''': photo of a metal sign which says "shuttering google reader / killed blogging", in all uppercase in a typical street-sign sans-serif font. It's designed to look very much like a real street sign, with the first three words being in the top half of the sign where the text is white on a dark blue background and the last two in the bottom half where the text is that same dark blue on a white background. * '''source''': [https://xoxo.zone/@mathowie/110633603793578943 xoxo.zone... wikitext text/x-wiki == Summary == * '''description''': photo of a metal sign which says "shuttering google reader / killed blogging", in all uppercase in a typical street-sign sans-serif font. It's designed to look very much like a real street sign, with the first three words being in the top half of the sign where the text is white on a dark blue background and the last two in the bottom half where the text is that same dark blue on a white background. * '''source''': [https://xoxo.zone/@mathowie/110633603793578943 xoxo.zone/@mathowie] d5e59156c827cc942b84977e9cff002f0f398359 883 882 2023-07-08T17:08:45Z Woozle 1 wikitext text/x-wiki == Summary == * '''description''': photo of a metal sign which says "shuttering google reader / killed blogging", in all uppercase in a typical street-sign sans-serif font. It's designed to look very much like a real street sign, with the first three words being in the top half of the sign where the text is white on a dark blue background and the last two in the bottom half where the text is that same dark blue on a white background. The sign is hanging on an interior door. * '''source''': [https://xoxo.zone/@mathowie/110633603793578943 xoxo.zone/@mathowie] a4d7408b79b951418fba21a90e4ca73e7972db2e 12 280 890 2023-07-12T13:52:02Z Woozle 1 Created page with "{{fmt/title|Hashtags on TootCat}} Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clic..." wikitext text/x-wiki {{fmt/title|Hashtags on TootCat}} Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. Some items of note: * Hashtags are not case-sensitive; #HashTag and #hashtag are functionally the same. * We encourage folks to camel-case hashtags, however, as this makes them more friendly for screen-reader software. * You can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * You can link to a hashtag from a post without tagging that post into the hashtag by linking to the hashtag feed URL. In TootCat, the [[Help:TootCat/HTML/formatting|syntax]] for this (using #softwareGripe as an example hashtag) is: <syntaxhighlight lang=html> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user </syntaxhighlight> ==Tags to Use== You can of course invent your own hashtags, but here are some particularly clever ones: * #florespondence - flower photos * #lichenSubscribe - photos of lichen * #mastoDog / #mastoDogs - photos of dogs * #mosstodon - photos of moss c0345a3263ae61f9b64d029c6b5b4ce78bc117dd 892 890 2023-07-12T14:24:34Z Woozle 1 wikitext text/x-wiki {{fmt/title|Hashtags on TootCat}} Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. Some items of note: * Hashtags are not case-sensitive; #HashTag and #hashtag are functionally the same. But note -- * We encourage folks to camel-case hashtags, however, as this makes them more friendly for screen-reader software. * You can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * You can link to a hashtag from a post without tagging that post into the hashtag by linking to the hashtag feed URL. In TootCat, the [[Help:TootCat/HTML/formatting|syntax]] for this (using #softwareGripe as an example hashtag) is: <syntaxhighlight lang=html> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user </syntaxhighlight> ==Tags to Use== You can of course invent your own hashtags, but here are some particularly clever ones (usually used for photos, but can also apply to text posts): * {{l/tc/hashtag|florespondence}} - flowers * {{l/tc/hashtag|lichenSubscribe}} - lichen * {{l/tc/hashtag|mastoDog}} / {{l/tc/hashtag|mastoDogs}} - dogs * {{l/tc/hashtag|mosstodon}} - moss ==Utility Tags== There are some tags which are used for spreading information which many users and admins consider to be important, and these should only be used for those topics. * {{l/tc/hashtag|fediblock}} is frequently abused by users (on other sites) who dislike the idea of fediblocking. Only use when you are trying to broadcast a legitimate fediblock advisory. There may be others, but so far that is the only one which has been problematic. 25614fa693435dc9cdadbf834a2d1d19dd311f3a 894 892 2023-07-21T14:08:35Z Woozle 1 /* Tags to Use */ wikitext text/x-wiki {{fmt/title|Hashtags on TootCat}} Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. Some items of note: * Hashtags are not case-sensitive; #HashTag and #hashtag are functionally the same. But note -- * We encourage folks to camel-case hashtags, however, as this makes them more friendly for screen-reader software. * You can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * You can link to a hashtag from a post without tagging that post into the hashtag by linking to the hashtag feed URL. In TootCat, the [[Help:TootCat/HTML/formatting|syntax]] for this (using #softwareGripe as an example hashtag) is: <syntaxhighlight lang=html> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user </syntaxhighlight> ==Tags to Use== You can of course invent your own hashtags, but here are some particularly clever ones (usually used for photos, but can also apply to text posts): {| class="wikitable sortable" |- ! Topic || Tags |- | cats || {{l/tc/hashtag|catstodon}} |- | cats: Saturday || {{l/tc/hashtag|caturday}} |- | dogs || {{l/tc/hashtag|mastoDog}} / {{l/tc/hashtag|mastoDogs}} |- | flowers || {{l/tc/hashtag|florespondence}} |- | lichen || {{l/tc/hashtag|lichenSubscribe}} |- | moss || {{l/tc/hashtag|mosstodon}} |- | Saturday: cats || {{l/tc/hashtag|caturday}} |} ==Utility Tags== There are some tags which are used for spreading information which many users and admins consider to be important, and these should only be used for those topics. * {{l/tc/hashtag|fediblock}} is frequently abused by users (on other sites) who dislike the idea of fediblocking. Only use when you are trying to broadcast a legitimate fediblock advisory. There may be others, but so far that is the only one which has been problematic. 3df7ba8fff7a94dfe8e62e1acea011b6b5eef1ef 897 894 2023-07-31T21:57:40Z Woozle 1 wikitext text/x-wiki {{fmt/title|Hashtags on TootCat}} Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. Some items of note: * Hashtags are not case-sensitive; #HashTag and #hashtag are functionally the same. But note -- * We encourage folks to camel-case hashtags, however, as this makes them more friendly for screen-reader software. * You can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * You can link to a hashtag from a post without tagging that post into the hashtag by linking to the hashtag feed URL. In TootCat, the [[Help:TootCat/HTML/formatting|syntax]] for this (using #softwareGripe as an example hashtag) is: <syntaxhighlight lang=html> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user </syntaxhighlight> ==Tags to Use== You can of course invent your own hashtags, but here are some particularly clever ones (usually used for photos, but can also apply to text posts): {| class="wikitable sortable" |- ! Topic || Tags |- | cats || {{l/tc/hashtag|catstodon}} |- | cats: Saturday || {{l/tc/hashtag|caturday}} |- | dogs || {{l/tc/hashtag|mastoDog}} / {{l/tc/hashtag|mastoDogs}} |- | flowers || {{l/tc/hashtag|bloomscrolling}}, {{l/tc/hashtag|florespondence}} |- | lichen || {{l/tc/hashtag|lichenSubscribe}} |- | mice || {{l/tc/hashtag|micetodon}}, {{l/tc/hashtag|mousetodon}} |- | moss || {{l/tc/hashtag|mosstodon}} |- | Saturday: cats || {{l/tc/hashtag|caturday}} |- | waterfalls || {{l/tc/hashtag|cataractivityPub}} |} ==Utility Tags== There are some tags which are used for spreading information which many users and admins consider to be important, and these should only be used for those topics. * {{l/tc/hashtag|fediblock}} is frequently abused by users (on other sites) who dislike the idea of fediblocking. Only use when you are trying to broadcast a legitimate fediblock advisory. There may be others, but so far that is the only one which has been problematic. 3e8fd3fbf3e7202c19d377eb98f459277d35fd0f 10 281 891 2023-07-12T14:01:34Z Woozle 1 Created page with "<span style="color: #888;">#</span>[https://toot.cat/tags/{{{1}}} {{{1}}}]" wikitext text/x-wiki <span style="color: #888;">#</span>[https://toot.cat/tags/{{{1}}} {{{1}}}] e793514554e8bba0a8da31d2e14776b2cc4f670d 12 248 893 852 2023-07-12T15:10:28Z Woozle 1 there's now a subpage about hashtags wikitext text/x-wiki ==Editing== * [[/HTML|using HTML]] ==Constrants== * '''Q: Do you have any language requirements (e.g. only post in English)?''' ** '''A:''' Any language is fine! *** We will use translation tools as needed to spot-check content, but we largely rely on other speakers to report users who are being problematic in languages we don't speak. *** For example: We had a small influx of Chinese users in 2022 when the PRC blocked access to Twitter; we're happy to offer a refuge for friendly people when that kind of thing happens. *** We also have a lot of French and German posters. *** ...and of course we encourage posting in [[Catalan]], because that's what the [[.cat]] TLD was originally created for (even if hardly anyone uses it that way anymore). ==Accounting for Cats== * '''Q: Where's the cat?''' ** '''A:''' see {{l/sub|cat-detector van}} * '''Q: Do I have to be a cat to have an account here?''' ** '''A:''' Not at all! We certainly welcome cats and other nonhumans as users, either directly or via their appointed agents, but you do not have to be feline or even nonhuman in order to sign up. * '''Q: Are dogs [other non-cat animals] welcome in photo toots?''' ** '''A:''' Absolutely! We welcome all species. Especially ferrets, wombats, possums, and capybaras. But dogs are cool too. ==How to Social== * '''Q: What are good ways to find mutuals?''' * '''Q: Are there community standards other than the site page?''' ** '''A:''' See [[Toot.cat/CoC|the CoC]]. * '''Q: Is it okay for me to have an account with the same username on another server?''' ** '''A:''' Absolutely! *** However, please don't go trashing us in other venues, inaccurately or unfairly representing us, or being a jerk. The internet is not a role-playing game, words have consequences, and there are things we don't want to be associated with. * '''Q: What can I expect the mods to do?''' ** '''A1:''' We will suspend or warn any of our users who are problematic; we remove spambot accounts as soon as they are spotted; we defederate from problematic instances. ** '''A2:''' We want this to be a bullshit-free zone, and we are happy to use our decades of online experience to help find solutions. * '''Q: What actions should I consider when I see something I don’t like (in my timeline, server, hashtag, etc)?''' ** '''A:''' Definitely use the reporting system, for starters. You can report individual posts and entire accounts. You may also feel free to message [[@woozle]] directly with questions. Reports go to all staff, however, and are more likely to result in quick action. * '''Q: What’s a CW good for?''' ** '''A:''' They were originally designed to let people skip topics they didn't want to deal with, but they're also very useful for [[/CWs|so many other things!]] * '''Q: How about hashtags?''' ** '''A:''' see {{l/sub|hashtags}} * '''Q: How do I ask for CW? What can I do when I don’t get it?''' ** '''A:''' This is a good question with no single right answer. The standard solution is to respond to the post you'd like CWed -- either publicly or as a DM (it's up to you) -- and ask for that post/subject to please be CWed. If that doesn't work, it's perfectly okay to contact the admins about it or even file a report (again, use your judgement). We ''usually'' will not penalize our users for failing to use CWs, but we may approach them directly about it if it has been reported. You are also free to block the user in question. *** Note that for those who don't like using CWs, another alternative is to use hashtags -- which can be filtered against by people who don't want to see certain types of content. *** I realize these answers don't completely solve the problem in all cases, so (as always) please feel to discuss them with me. -- [[@woozle]] ==Accounts: Technical== * '''Q: I want to delete my account, but I've lost access. Can you do this for me?''' ** '''A1:''' If you have access to the email address associated with the account, you can request a password reset [https://toot.cat/auth/password/new here]. ** '''A2:''' If you aren't sure what email account is associated with it, you can ask an admin to look it up. ** '''A3:''' If you no longer have access to the email account, then we'll have to discuss the situation further to make sure you are actually the account holder. ==Archive== * [[text2toot]]: We had an SMS UI for awhile, but it was high-maintenance and nobody was using it, so it has been discontinued. 7655b2327d312821d8ed8a5951013ed838a5f57b 0 162 896 510 2023-07-25T20:29:55Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:mastodon]] [[category:limited]] * '''site''': https://union.place ==About== [[union.place]] (u.p) is a Mastodon instance specifically for workers' unions. ==TootCat History== * '''2023-07-23''' TC [https://toot.cat/@news/110765664009616524 unsuspends] u.p after a review of the situation. U.p. does not itself allow the presence of police unions as users, and AFL/CIO is not one union but an inter-union alliance. * '''2022-11-26''' TC silences u.p as planned. * '''2022-11-14''' TC [https://toot.cat/@news/109343526830497124 announces plan] to suspend u.p on 2022/11/26, for allowing presence of {{l/wp|AFL–CIO}}, a union known for racism<ref name=SocWork /> and the support of police unions.<ref name=NewRep /> ==Footnotes== <references> <ref name=NewRep>'''2020-05-29''' [https://newrepublic.com/article/157918/no-cop-unions No More Cop Unions] {{fmt/quote|The International Union of Police Associations, which represents over 100,000 law enforcement employees as well as emergency medical personnel, is officially affiliated with the}} AFL-CIO... {{fmt/quote|But if the federation wants to prove that it’s seriously committed to racial justice and true worker solidarity, the AFL-CIO must permanently disaffiliate from the IUPA and sever its ties with any and all other police associations.}}</ref> <ref name=SocWork>'''1986-01''' [http://socialistworker.org/2012/06/28/blacks-and-the-great-depression Blacks and the Great Depression] talks about the history of racism in the AFL; it's not clear if this is still a problem.</ref> </references> c773fdcff10a174fe5445746d8b16dc2b2c8778b 0 282 898 2023-08-20T18:44:41Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] * '''site''': [https://mstdn.party mstdn.party] ==History== * '''2023-08-20''' Received a request ([https://mstdn.ca/@austin/110923..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] * '''site''': [https://mstdn.party mstdn.party] ==History== * '''2023-08-20''' Received a request ([https://mstdn.ca/@austin/110923309066545623 DM]) from [https://mstdn.ca/@austin mstdn.ca/@austin], who apparently became instance admin this past April, to remove the silence. Checking the admin panel for more information; it looks like the limit was imposed so long ago that there's no event-log of when it was done. The description is only {{fmt/quote|Ongoing failure to moderate racist user}}. Limit removed. 72ac0af4d21bd45825cf4006726d70e8f3220cbb 6 283 899 2023-08-27T12:11:56Z Woozle 1 [[category:screenshot]] [[category:transphobia]] wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:transphobia]] 95395139ee0e0d99bb091225200bcc04f0a8f0bc 900 899 2023-08-27T12:13:24Z Woozle 1 wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:transphobia]] [[category:disinformation]] John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}} -- this is untrue. 32c6eeed41ea1bffcb4187a113a486f4889131a2 901 900 2023-08-27T12:15:49Z Woozle 1 /* Summary */ wikitext text/x-wiki == Summary == [[category:screenshot]] [[category:transphobia]] [[category:disinformation]] John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}} and {{fmt/quote|they are fundamentally still men}} -- both are untrue. 6389360b5a2e59c49eb74c566a1ca0405115a72d 0 284 902 2023-08-27T12:16:25Z Woozle 1 Created page with "[[category:instance]] File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentall..." wikitext text/x-wiki [[category:instance]] [[File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentally still men}}]] ==History== * '''2023-08-24''' [https://linuxrocks.online/@gothnbass/110944728945334744 linuxrocks.online/@gothnbass] reports being warned for (correctly) reporting transphobia, as seen in [[:File:B269edd54f6fcffa.png|this screenshot]]. 66effad38c206e3d977441825d39f9aa98556a79 903 902 2023-08-27T12:18:06Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentally still men}}]] * '''domain''': {{ls/domain|linuxrocks.online}} ==History== * '''2023-08-24''' [https://linuxrocks.online/@gothnbass/110944728945334744 linuxrocks.online/@gothnbass] reports being warned for (correctly) reporting transphobia, as seen in [[:File:B269edd54f6fcffa.png|this screenshot]]. See also the note about @piejacker, whose account is still active, in [[@Woozle/malusers]]. 1847e2c8d50a1ea9c8b842cb9047ef0a548ea895 904 903 2023-08-27T12:23:11Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentally still men}}]] * '''domain''': {{ls/domain|linuxrocks.online}} ==History== * '''2023-08-24''' [https://linuxrocks.online/@gothnbass/110944728945334744 linuxrocks.online/@gothnbass] ([https://web.archive.org/web/20230827122128/https://linuxrocks.online/@gothnbass/110944728945334744 archive.org]) reports being warned for (correctly) reporting transphobia, as seen in [[:File:B269edd54f6fcffa.png|this screenshot]]. See also the note about @piejacker, whose account is still active, in [[@Woozle/malusers]]. 5819c3554fd9832d01f1debbda685a451f54d6b0 905 904 2023-08-27T16:56:56Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:transphobia]] [[File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentally still men}}]] * '''domain''': {{ls/domain|linuxrocks.online}} ==History== * '''2023-08-27''' Received report of [https://linuxrocks.online/@linuxtechmore/110953292842964460 this post]: {{fmt/quote|Why do you believe you can silence those who disagree with transgenderism? Why impose your ideologies on them? And why label opposition to transgenderism as a phobia? Your actions themselves are a form of phobia.}} I have silenced the instance. &ndash;[[@Woozle]] * '''2023-08-24''' [https://linuxrocks.online/@gothnbass/110944728945334744 linuxrocks.online/@gothnbass] ([https://web.archive.org/web/20230827122128/https://linuxrocks.online/@gothnbass/110944728945334744 archive.org]) reports being warned for (correctly) reporting transphobia, as seen in [[:File:B269edd54f6fcffa.png|this screenshot]]. See also the note about @piejacker, whose account is still active, in [[@Woozle/malusers]]. bfc74b91b30429c0a4920026a8b55bd7e43dd45f 906 905 2023-08-27T16:59:40Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:transphobia]] [[category:silenced]] [[File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentally still men}}]] * '''domain''': {{ls/domain|linuxrocks.online}} ==History== * '''2023-08-27''' Received report of [https://linuxrocks.online/@linuxtechmore/110953292842964460 this post]: {{fmt/quote|Why do you believe you can silence those who disagree with transgenderism? Why impose your ideologies on them? And why label opposition to transgenderism as a phobia? Your actions themselves are a form of phobia.}} I have silenced the instance. &ndash;[[@Woozle]] * '''2023-08-24''' [https://linuxrocks.online/@gothnbass/110944728945334744 linuxrocks.online/@gothnbass] ([https://web.archive.org/web/20230827122128/https://linuxrocks.online/@gothnbass/110944728945334744 archive.org]) reports being warned for (correctly) reporting transphobia, as seen in [[:File:B269edd54f6fcffa.png|this screenshot]]. See also the note about @piejacker, whose account is still active, in [[@Woozle/malusers]]. 0e28f8f2e487601164e14758599d772bec75fbb6 909 906 2023-08-27T17:03:07Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:transmisia]] [[category:silenced]] [[File:B269edd54f6fcffa.png|thumb|John Bell: {{fmt/quote|For some women, their problems ARE that trans women exist}}... {{fmt/quote|they are fundamentally still men}}]] * '''domain''': {{ls/domain|linuxrocks.online}} ==History== * '''2023-08-27''' Received report of [https://linuxrocks.online/@linuxtechmore/110953292842964460 this post]: {{fmt/quote|Why do you believe you can silence those who disagree with transgenderism? Why impose your ideologies on them? And why label opposition to transgenderism as a phobia? Your actions themselves are a form of phobia.}} I have silenced the instance. &ndash;[[@Woozle]] * '''2023-08-24''' [https://linuxrocks.online/@gothnbass/110944728945334744 linuxrocks.online/@gothnbass] ([https://web.archive.org/web/20230827122128/https://linuxrocks.online/@gothnbass/110944728945334744 archive.org]) reports being warned for (correctly) reporting transphobia, as seen in [[:File:B269edd54f6fcffa.png|this screenshot]]. See also the note about @piejacker, whose account is still active, in [[@Woozle/malusers]]. 5409458aae70af07f96bc36e3a76fb9f15d79268 14 285 907 2023-08-27T17:02:05Z Woozle 1 Redirected page to [[Category:Transmisia]] wikitext text/x-wiki #redirect [[:category:transmisia]] 97cde072e9bb1e89dc49b9eff2e85936c70e11a0 14 286 908 2023-08-27T17:02:30Z Woozle 1 Created page with "items relating to transmisia/transphobia" wikitext text/x-wiki items relating to transmisia/transphobia 051179779111211edc0b0f851c2ecfe078552d88 0 241 910 777 2023-08-27T17:06:31Z Woozle 1 wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] [[category:transmisia]] [[category:dead]] * '''site''': {{ls/domain|mastodon.lol}} ==Discussion== * '''2023-02-09 15:29''' [https://kolektiva.social/@YKantRachelRead/109836668497694836 kolektiva.social/@YKantRachelRead] {{fmt/quote|I'm reading over the thread on mastodon.lol where the moderation team states that they won't allow people to spoil hogwarts legacy, and their main rationale seems to be, "but other instances might defederate from us if we allow this behavior to continue!"}} * '''2023-02-09 15:20''' [https://mastodon.lol/@nathan/109836633022272265 mastodon.lol/@nathan] (admin) {{fmt/quote|Mastodon.lol will shut down on May 9, 2023, 3 months from today.}} * '''2023-02-09 14:37''' [https://mastodon.lol/@TheSunnyOne/109836463083876908 mastodon.lol/@TheSunnyOne] {{fmt/quote|They really do just think it's abut misgendering, don't they?}} ... {{fmt/quote|Oh, and once again equating sharing spoilers to actual harm.}} (includes screenshot of [https://mastodon.lol/@ColinRSykes Colin Sykes] calling the poster "scum" - fortunately he seems to have been suspended) cb9b72a7bfa33df9e211871a559d65d713574da3 0 287 911 2023-08-29T12:25:41Z Woozle 1 Created page with "[[category:instance]] ==History== * '''2023-08-29''' [https://tech.lgbt/@mods/110972278089012287 tech.lgbt] is fediblocking them" wikitext text/x-wiki [[category:instance]] ==History== * '''2023-08-29''' [https://tech.lgbt/@mods/110972278089012287 tech.lgbt] is fediblocking them 80ca6017c254eee2e8a23344272c4f7f46706f70 912 911 2023-08-29T12:26:51Z Woozle 1 wikitext text/x-wiki [[category:instance]] ==History== * '''2023-08-29''' [https://tech.lgbt/@mods/110972278089012287 tech.lgbt] is fediblocking them; see also note about [[mstdn.jp]] 4b26d88a24e1c0297014db6146116c3e486b5768 0 288 913 2023-09-07T11:53:21Z Woozle 1 Created page with "[[category:instance]] ==Events== * '''2023-09-05''' [https://rage.love/@admin/111015410883804145 rage.love/@admin] reports that {{fmt/quote|victor @ tooters.org, the admin and..." wikitext text/x-wiki [[category:instance]] ==Events== * '''2023-09-05''' [https://rage.love/@admin/111015410883804145 rage.love/@admin] reports that {{fmt/quote|victor @ tooters.org, the admin and owner of tooters.org, has been trolling, menacing, and spreading misinformation about other admins for their server moderation choices}}, and recommends a fediblock. Details and screenshots are included. 7b308bafd4d534df8fb8fb00e3eb682fc728ba54 0 42 914 637 2023-09-13T18:56:57Z Woozle 1 wikitext text/x-wiki [[category:TLD]] The .cat [[htyp:top-level domain|TLD]] has some [https://contract.gandi.net/v5/contracts/14600/special_conditions_CAT_1.3.pdf unusual requirements]. Toot.Cat attempts to satisfy these requirements via the following: * We run the Mastodon software (our primary mission), whose interface is available in Catalan. * We collect information about [[Catalonia]] as it comes our way. * We are interested in making space for content related to Catalonia and/or [[Catalan]]. ==Non-Catal* .cat domains== There are a number of other <code>.cat</code> domains currently being used for purposes that are not focused on Catalonia or Catalan; as with TootCat, their primary means of satisfying the requirements appears to be that they provide Catalan as an interface language: * {{ls/domain|blob.cat}}: a [[Pleroma]] instance * {{ls/domain|high.cat}}: another {{lc|Mastodon}} instance * {{ls/domain|http.cat}} * {{ls/domain|nyan.cat}} ==Notes== Hearsay is that the .cat admins used to be much stricter, but have now loosened enforcement a bit. (Reference post no longer available.) e17f00ad6e8e734b202b4ecad2feae8dabc1c3d2 14 289 915 2023-09-13T18:58:45Z Woozle 1 Created page with "'''TLD'''s (top-level domains) for which we have wiki pages" wikitext text/x-wiki '''TLD'''s (top-level domains) for which we have wiki pages 4c76020a85b2bc84d205bd2ae3e2e62f03ff26b0 0 62 916 819 2023-10-06T22:58:49Z Woozle 1 /* NSK Content Warnings */ wikitext text/x-wiki =Code of Conduct= ==Meta== This is not a contract. This is a guideline to help you understand how we, as a community, see and evaluate different kinds of behavior. We will always try to leave room for honest mistakes and misunderstandings, but we reserve the right to act without regard to strict or exacting interpretation of these guidelines. They are a statement of intention, and they are intended to reflect the views of the TootCat community. If you have comments or questions, please feel free to reach out to the TootCat Uberwensch ([https://toot.cat/@woozle @woozle]) whether or not you are a TootCat member. ^.^ ==General== As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users. We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination. We try to empower our users and encourage them to act against any abuses of the Code of Conduct, in order to ensure that TootCat remains an oppression-free experience. Examples of unacceptable behavior include: <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>{{l/sub|red flags}} (a couple of specific examples)</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Activity / Self-Promotion ('''[[/self-promo|&gt;&gt;]]''')== {{i/sub|self-promo}} ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== Note that these are ''guidelines'', not hard-and-fast rules. We're not going to take action against posts that technically violate these requirements unless we feel there is a compelling reason to do so. ''<small>(The text below is more or less verbatim from the original CoC when TootCat originally went live, when its founders were in somewhat uncharted waters, and it may have even have been copied directly from some legally-advised boilerplate. We'll modify it as needs arise, but please don't take it too seriously. We're more concerned about people ''being'' dicks than posting them. ...but yeah, please CW dick pics. Eventually society will get less uptight about nudity and then we can have fewer rules. &mdash;[[@woozle]])</small>'' <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> ==Footnotes== {{i/val|page={{PAGENAME}}/self-promo|refs}} a664d545cf9334a6e2429e1ced82cbca8e8ab408 0 62 917 916 2023-10-07T00:50:59Z Woozle 1 /* NSK Content Warnings */ wikitext text/x-wiki =Code of Conduct= ==Meta== This is not a contract. This is a guideline to help you understand how we, as a community, see and evaluate different kinds of behavior. We will always try to leave room for honest mistakes and misunderstandings, but we reserve the right to act without regard to strict or exacting interpretation of these guidelines. They are a statement of intention, and they are intended to reflect the views of the TootCat community. If you have comments or questions, please feel free to reach out to the TootCat Uberwensch ([https://toot.cat/@woozle @woozle]) whether or not you are a TootCat member. ^.^ ==General== As tooters on this instance, we pledge to uphold an environment that is radically inclusive with respect for all users. We are committed to making participation in this instance an oppression-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. We define oppression as any language or action that expresses, reinforces, upholds or sympathizes with any form of systemic social domination. We try to empower our users and encourage them to act against any abuses of the Code of Conduct, in order to ensure that TootCat remains an oppression-free experience. Examples of unacceptable behavior include: <ul> <li>Personal attacks</li> <li>Trolling or insulting/derogatory comments</li> <li>Public or private oppressive language or actions</li> <li>Other unethical conduct</li> <li>{{l/sub|red flags}} (a couple of specific examples)</li> </ul> <p>Certain types of content should posted in such a way that you avoid showing it to non-consenting parties. These types of content should:</p> <ul> <li>Not be used a profile picture</li> <li>Be posted with media marked as sensitive</li> <li>Not be posted to the public timeline</li> </ul> <p>the above rules apply to content that is:</p> <ul> <li>Violent</li> <li>Flashing or rapidly changing</li> </ul> ==Creative Works== Always give credit to the artist for work that you post. A link back to the artist's original post will do, but feel free to give more details (name of artist, work from which the art is excerpted, or anything else that seems relevant). ==Bots== Bots that autofollow will be banned on sight, even if they respect #nobots, because: :(a) now that [https://toot.cat/@woozle/103773659877861786 relays] exist, they really aren't necessary, and :(b) they can be used by rogue instances as a means of letting their users circumvent blocks, which is a violation of safety and privacy needs. (This was implemented after appoval by a [https://toot.cat/@news/103768005256733940 poll of toot.cat users] posted on 2020-03-05.) ==Commercial Activity / Self-Promotion ('''[[/self-promo|&gt;&gt;]]''')== {{i/sub|self-promo}} ==Nudity / Sex / Kink (NSK)== ===NSK Content Warnings=== Note that these are ''guidelines'', not hard-and-fast rules. We're not going to take action against posts that technically violate these requirements unless we feel there is a compelling reason to do so. ''<small>(The text below is more or less verbatim from the original CoC when TootCat originally went live, when its founders were in somewhat uncharted waters, and it may have even have been copied directly from some legally-advised boilerplate. We'll modify it as needs arise, but please don't take it too seriously. We're more concerned about people ''being'' dicks than posting them. ...but yeah, please CW dick pics. Over time, we learn how to get along better with each other and there comes to be less trauma and anxiety around things like nudity. The more progress we make as a society, the fewer rules we will need. &mdash;[[@woozle]])</small>'' <p>Nudity is allowed without a CW as long as no genitals or nipples are shown</p> <ul> <li>If they are visible in the image they must be censored</li> <li>Nipple censoring pertains to any gender</li> </ul> <p>Any sexual imagery must be hidden as a sensitive image</p> <ul> <li>Sexual imagery is considered to be any sex / kink act regardless of clothing state / nudity</li> <li>Sexual imagery and nudity are distinct concepts</li> <li>No illegal imagery is allowed regardless of CW state</li> </ul> <p>NSK with a CW do not need to be censored in any way</p> <p>Violation of the content warning rules will</p> <ul> <li>An immediate silence when its violated on the federation timeline</li> <li>A domain silence when its violated by multiple parties on an instance</li> <li>A warning and admin editing your content when its violated by toot.cat users</li> </ul> ===NSK Consent To Post=== <p>NSK should not have other users tagged without their explicit prior consent</p> <p>Posting NSK that is not of yourself needs to include attribution to the person(s) visible, in such a way that clearly expresses their consent to have that imagery posted</p> <p>Violation of the consent to post rule will result in</p> <ul> <li>An immediate suspension when its violated on the federation timeline</li> <li>A domain suspension when its violated by multiple parties on an instance</li> <li>1 warning, followed by account deletion when violated by toot.cat users</li> </ul> <p>toot.cat supports and invites sex workers to join our community and will not tolerate any harassment or slurs made at or about sex workers (e.g. "prostitute", "hooker", "whore")</p> ==Closing== <p>By adopting this Code of Conduct, users commit themselves to fairly and consistently applying these principles to every aspect of using this instance. users who do not follow or enforce the Code of Conduct may be permanently banned.</p> <p>This Code of Conduct applies both to toots on toot.cat and to public spaces when an individual is representing toot.cat or its community.</p> <p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident.</p> ==Footnotes== {{i/val|page={{PAGENAME}}/self-promo|refs}} fbe918530b412b41ca5bd6974372cc119cfc119c 12 280 918 897 2023-12-08T16:27:50Z Woozle 1 wikitext text/x-wiki {{fmt/title|Hashtags on TootCat}} Adding a hashtag to a public post means that the post will be listed whenever anyone searches for that hashtag (which you can do just by clicking on any example of the same hashtag). It doesn't work with user-profiles, unfortunately; this seems like a missed opportunity which we hope to eventually address. Some items of note: * Hashtags are not case-sensitive; #HashTag and #hashtag are functionally the same. But note -- * We encourage folks to camel-case hashtags, however, as this makes them more friendly for screen-reader software. * You can subscribe to hashtags in much the same way as following another user -- posts with a hashtag to which you are subscribed will appear in your notifications. * You can link to a hashtag from a post without tagging that post into the hashtag by linking to the hashtag feed URL. In TootCat, the [[Help:TootCat/HTML/formatting|syntax]] for this (using #softwareGripe as an example hashtag) is: <syntaxhighlight lang=html> * #<a href="https://toot.cat/tags/softwareGripe">softwareGripe</a> - link to a hashtag feed without indexing the post containing the link * #<a href="https://toot.cat/@woozle/tagged/softwareGripe">softwareGripe @ Woozle</a> - link to only posts in that hashtag by a specific user </syntaxhighlight> ==Tags to Use== You can of course invent your own hashtags, but here are some particularly clever ones (usually used for photos, but can also apply to text posts): {| class="wikitable sortable" |- ! Topic || Tags |- | cats || {{l/tc/hashtag|catstodon}} |- | cats: Saturday || {{l/tc/hashtag|caturday}} |- | dogs || {{l/tc/hashtag|mastoDog}} / {{l/tc/hashtag|mastoDogs}} |- | flowers || {{l/tc/hashtag|bloomScrolling}}, {{l/tc/hashtag|florespondence}} |- | fungi || {{l/tc/hashtag|sporespondence}} |- | lichen || {{l/tc/hashtag|lichenSubscribe}} |- | mice || {{l/tc/hashtag|micetodon}}, {{l/tc/hashtag|mousetodon}} |- | moss || {{l/tc/hashtag|mosstodon}} |- | Saturday: cats || {{l/tc/hashtag|caturday}} |- | waterfalls || {{l/tc/hashtag|catarActivityPub}} |} ==Utility Tags== There are some tags which are used for spreading information which many users and admins consider to be important, and these should only be used for those topics. * {{l/tc/hashtag|fediblock}} is frequently abused by users (on other sites) who dislike the idea of fediblocking. Only use when you are trying to broadcast a legitimate fediblock advisory. There may be others, but so far that is the only one which has been problematic. 598911113546246bc37858e5a51f8aaedc85b826 6 290 919 2023-12-27T20:33:45Z Woozle 1 [[category:screenshot]] wikitext text/x-wiki == Summary == [[category:screenshot]] dc2a039a71f4df6b0291834b1b96ac10f518e061 0 291 920 2023-12-27T20:52:54Z Woozle 1 Created page with "==2023-12-27 - Woozle== ([https://mstdn.social/@walterdunham/111631922561972003 2023-12-23 16:45] Walter said (responding to [https://mstdn.social/@Free_Press/1116317655414886..." wikitext text/x-wiki ==2023-12-27 - Woozle== ([https://mstdn.social/@walterdunham/111631922561972003 2023-12-23 16:45] Walter said (responding to [https://mstdn.social/@Free_Press/111631765541488692 Aure Free Press]): <blockquote> <poem> @Free_Press The "chosen people" of God is annihilating an entire race! #Genocide #GenocideInGaza </poem> </blockquote> [https://toot.cat/@woozle/111653734457708128 13:13] Woozle commented: <blockquote> @walterdunham @Free_Press <blockquote> &lt;s&gt;<s>The "chosen people" of God</s>&lt;/s&gt; '''A bloodthirsty authoritarian leader''' is annihilating an entire race! </blockquote> Fixed. (How would you like to be held accountable for every action of your government, hmm?) </blockquote> [https://mstdn.social/@walterdunham/111653906505120686 13:56] Walter said: <blockquote> @woozle @Free_Press Seriously? That's your reply? It's fine IF ALL of Israel's citizenry is up in arms for this genocidal act. But no, half if not more than majority of Israel's populace are pro-zionist, and this is where the problem lies! They voted Netanyahu and his zionist government THRICE!!! If that doesn't tell you something then you are caught up in your own extremely consevative rightist world! Wher are you from? Are you from one of those "high and mighty" colonizing countries, grama?! </blockquote> [https://toot.cat/@woozle/111653920892765717 14:00] Woozle replied: <blockquote> @walterdunham @Free_Press Okay, so I'd say please just be clear that you're talking about Zionist zealots in particular and not all Jewish people or even all Israeli citizens. Also, voting for someone does not mean you approve of everything they do. Someone winning an election also does not necessarily mean the majority wanted them, even if you assume no electoral fraud. Sometimes the alternatives are worse; sometimes the vote is "legally" rigged (Gerrymandering, Electoral College shenanigans, etc.) and of course people can be vastly misinformed about what their vote means. I'm from the US, and I voted for Biden in the general election -- but that doesn't mean I support everything he does, much less everything the US has ever done. </blockquote> [https://mstdn.social/@walterdunham/111653944791281648 14:06] Walter said: <blockquote> @woozle @Free_Press Am not clear eough for you? Didn't I say "zionist" in the very beginning? I'm AWARE that not ALL Jews are zionists as there are in fact anti-Netanyahu protests in Israel (albeit very small pockets!). "Also, voting for someone does not mean you approve of everything they do." THAT IS THE ESSENCE OF VOTING for a candidate. And in case you missed it, I said they voted Netanyahu to power THRICE!!! Does that not tell you these zionists jews WHO VOTED HIM IN like what he's doing? </blockquote> [https://toot.cat/@woozle/111653953030080592 14:08] Woozle replied: <blockquote> @walterdunham @Free_Press I don't see "Zionist" anywhere in there. [[File:F65c557e6987ab79.png]] </blockquote> [https://toot.cat/@woozle/111653962498090047 14:11] Woozle replied: <blockquote> @walterdunham @Free_Press <blockquote>"Also, voting for someone does not mean you approve of everything they do." THAT IS THE ESSENCE OF VOTING for a candidate.</blockquote> Um, no. It's very rarely (if ever) possible to find a candidate who one even thinks will do everything one wants -- much less one who will actually carry through with it. </blockquote> [https://mstdn.social/@walterdunham/111653968399018608 14:12] Walter said: @woozle @Free_Press Again I repeat, THEY VOTED NETANYAHU TO OFFICE THREE TIMES!!! [https://mstdn.social/@walterdunham/111653971934993452 14:13] Walter said: <blockquote> @woozle@toot.cat @Free_Press Nitpicking will not work well for you. You're just being argumentative now! Just give it up as you have already shown where your sympathy lies!!! </blockquote> At this point Walter started doing something so that I couldn't reply, despite still seeing his posts in my notifs, so I didn't get the chance to point out that Israeli support for Netanyahu was 39% ''after'' the uptick in support from the initial attack. (It's kind of horrendous that bombing another country would cause an ''uptick'' in support, but that's a separate issue.): * '''2023-05-20''' [https://www.timesofisrael.com/support-for-netanyahu-goes-up-but-voters-unhappy-with-policies-for-haredim-poll/ Support for Netanyahu goes up, but voters unhappy with policies for Haredim — poll] I wasn't able to quickly find any more recent polls, but I'd hope support has gone down since then as folks have started to gain a better appreciation of the horror being inflicted on innocent people. 838fad1b44ef19ac48561d146f03c563ac87ba3c 922 920 2023-12-27T20:58:15Z Woozle 1 screenshot of full discussion wikitext text/x-wiki ==2023-12-27 - Woozle== [[File:2023-12-27 at 15-53-04.screen.Walter Dunham Ll.B. (@walterdunham@mstdn.social).crop.png|thumb]] ([https://mstdn.social/@walterdunham/111631922561972003 2023-12-23 16:45] Walter said (responding to [https://mstdn.social/@Free_Press/111631765541488692 Aure Free Press]): <blockquote> <poem> @Free_Press The "chosen people" of God is annihilating an entire race! #Genocide #GenocideInGaza </poem> </blockquote> [https://toot.cat/@woozle/111653734457708128 13:13] Woozle commented: <blockquote> @walterdunham @Free_Press <blockquote> &lt;s&gt;<s>The "chosen people" of God</s>&lt;/s&gt; '''A bloodthirsty authoritarian leader''' is annihilating an entire race! </blockquote> Fixed. (How would you like to be held accountable for every action of your government, hmm?) </blockquote> [https://mstdn.social/@walterdunham/111653906505120686 13:56] Walter said: <blockquote> @woozle @Free_Press Seriously? That's your reply? It's fine IF ALL of Israel's citizenry is up in arms for this genocidal act. But no, half if not more than majority of Israel's populace are pro-zionist, and this is where the problem lies! They voted Netanyahu and his zionist government THRICE!!! If that doesn't tell you something then you are caught up in your own extremely consevative rightist world! Wher are you from? Are you from one of those "high and mighty" colonizing countries, grama?! </blockquote> [https://toot.cat/@woozle/111653920892765717 14:00] Woozle replied: <blockquote> @walterdunham @Free_Press Okay, so I'd say please just be clear that you're talking about Zionist zealots in particular and not all Jewish people or even all Israeli citizens. Also, voting for someone does not mean you approve of everything they do. Someone winning an election also does not necessarily mean the majority wanted them, even if you assume no electoral fraud. Sometimes the alternatives are worse; sometimes the vote is "legally" rigged (Gerrymandering, Electoral College shenanigans, etc.) and of course people can be vastly misinformed about what their vote means. I'm from the US, and I voted for Biden in the general election -- but that doesn't mean I support everything he does, much less everything the US has ever done. </blockquote> [https://mstdn.social/@walterdunham/111653944791281648 14:06] Walter said: <blockquote> @woozle @Free_Press Am not clear eough for you? Didn't I say "zionist" in the very beginning? I'm AWARE that not ALL Jews are zionists as there are in fact anti-Netanyahu protests in Israel (albeit very small pockets!). "Also, voting for someone does not mean you approve of everything they do." THAT IS THE ESSENCE OF VOTING for a candidate. And in case you missed it, I said they voted Netanyahu to power THRICE!!! Does that not tell you these zionists jews WHO VOTED HIM IN like what he's doing? </blockquote> [https://toot.cat/@woozle/111653953030080592 14:08] Woozle replied: <blockquote> @walterdunham @Free_Press I don't see "Zionist" anywhere in there. [[File:F65c557e6987ab79.png]] </blockquote> [https://toot.cat/@woozle/111653962498090047 14:11] Woozle replied: <blockquote> @walterdunham @Free_Press <blockquote>"Also, voting for someone does not mean you approve of everything they do." THAT IS THE ESSENCE OF VOTING for a candidate.</blockquote> Um, no. It's very rarely (if ever) possible to find a candidate who one even thinks will do everything one wants -- much less one who will actually carry through with it. </blockquote> [https://mstdn.social/@walterdunham/111653968399018608 14:12] Walter said: @woozle @Free_Press Again I repeat, THEY VOTED NETANYAHU TO OFFICE THREE TIMES!!! [https://mstdn.social/@walterdunham/111653971934993452 14:13] Walter said: <blockquote> @woozle@toot.cat @Free_Press Nitpicking will not work well for you. You're just being argumentative now! Just give it up as you have already shown where your sympathy lies!!! </blockquote> At this point Walter started doing something so that I couldn't reply, despite still seeing his posts in my notifs, so I didn't get the chance to point out that Israeli support for Netanyahu was 39% ''after'' the uptick in support from the initial attack. (It's kind of horrendous that bombing another country would cause an ''uptick'' in support, but that's a separate issue.): * '''2023-05-20''' [https://www.timesofisrael.com/support-for-netanyahu-goes-up-but-voters-unhappy-with-policies-for-haredim-poll/ Support for Netanyahu goes up, but voters unhappy with policies for Haredim — poll] I wasn't able to quickly find any more recent polls, but I'd hope support has gone down since then as folks have started to gain a better appreciation of the horror being inflicted on innocent people. 650a158d50fd20324a3066774db5f3d098ad3e20 6 292 921 2023-12-27T20:56:29Z Woozle 1 [[category:screenshot]] wikitext text/x-wiki == Summary == [[category:screenshot]] dc2a039a71f4df6b0291834b1b96ac10f518e061 0 44 923 838 2023-12-30T19:44:04Z Woozle 1 wikitext text/x-wiki __NOTOC__ =Woozle's Fediverse Hall of Shame= The primary purpose of this page is to encourage accountability for bad behavior in the Mastodon fediverse. It's pretty minimal, but it's what we currently have time for; larger projects are currently underway. These users have generally not been blocked on toot.cat because I want to keep an eye on them, but I will do so without warning if it seems appropriate. If you disagree with any of these listings, or have suggestions for additional listings, please submit them to [https://toot.cat/@woozle woozle@toot.cat]. {| class=wikitable |- ! User !! Domain !! Software !! Examples |- | [https://pl.smuglo.li/users/Azurolu Azurolu] | {{ls/domain|pl.smuglo.li}}<ref name=smuglo /> | Pleroma | * [https://pl.smuglo.li/objects/05513a26-2880-48e9-95d5-0bf533423f07 mocking] of [https://blog.usejournal.com/mastodons-complicated-relationship-with-queer-activism-6b82487f8909 thoughtful article written by a Mastodon user], inviting a pile-on, rather than {{l/ip|addressing the content}} * [https://pl.smuglo.li/objects/ff85e0ed-1950-4478-987c-bebe8f99b671 "autism" used as a put-down], and another pointless attack on same article |- | [https://quitter.se/strypey Danyl Stripe] | {{ls/domain|quitter.se}} | GNU Social | * '''2018-03-17''' [http://quitter.se/notice/24379306 fediverse thread] * '''2018-02-28''' [https://twitter.com/DanylStrype/status/968888060942454784 Tweet] |- | [https://voluntaryism.club/users/dtluna dtluna] | {{ls/domain|voluntaryism.club}} | Pleroma | * '''2018-07-25''' suspended in response to a report of repeated offensive speech &ldquo;I don't know all the specifics about Somalia to answer this question. But neither does any nigger who says "Somalia is a libertarian paradise!"&rdquo; -- though it should be noted that it was all at least 8 months ago [https://pleroma.soykaf.com/objects/e94062b3-07d3-4b47-add5-901587f14361] [https://pleroma.soykaf.com/objects/4f6be882-999d-45d3-b08c-c7c4aab1b092] [https://pleroma.soykaf.com/objects/cacdb973-2720-4885-9e1b-ab76c954becd] * '''2018-04-14''' thread in response to [https://toot.cat/@woozle/99860546818348091 Be the traffic from the left you wish to see in the world.] |- | [https://libertarianism.club/users/dtluna dtluna] | {{ls/domain|libertarianism.club}} | (defunct) | * '''2018-03-28''' [https://toot.cat/web/statuses/99716767828947396] "You dumb niggers *cannot* even understand why government doesn't exist." |- | [https://lor.sh/@dump_stack dump_stack] | {{ls/domain|lor.sh}} | Mastodon | * '''2020-02-24''' [https://lor.sh/@dump_stack/103715838645490658] "people have anti-homeless attitudes because most of the time being homeless is a choice not a matter of chance." |- | [https://linuxrocks.online/@Piejacker875 Piejacker] | {{ls/domain|linuxrocks.online}} | Mastodon | * '''2018-06-29''' [https://linuxrocks.online/@Piejacker875/100291700468993514 Are the concentration camps holding people that formerly held citizenship?]: implies that it's ok to put people in concentration camps as long as they aren't citizens * Also generally known for {{l/ip|sea-lioning}} (no links currently collected). |- | [https://mastodon.social/@rotatingskull RotatingSkull] | {{ls/domain|mastodon.social}} | Mastodon | * '''2018-06-30''' [https://mastodon.social/@rotatingskull/100295441847774574 thread]: haranguing ** Note that Hoodie's post was on 6/29 but RS chose to make this comment midway into the #ForkTogether meeting. * '''2018-03-06''' [https://computerfairi.es/@kiilas/99632321234054344# thread] ** [https://toot.cat/web/statuses/99632321205503971 toot.cat] ** [http://archive.is/HC957 archive.is] (does not include toot contents, but is at least useful for preserving log of toots in case any are deleted later) |- | [https://zirk.us/@dambaras dambaras] ([https://chass.ncsu.edu/people/dambaras/ David Ambaras]) | {{ls/domain|zirk.us}} | Mastodon | * '''2023-04-06''' [https://web.archive.org/web/20230406141102/https://zirk.us/@dambaras/110149627484335327 response]: replying to my post with insult, and never backing down |- | [[Mstdn.social/@walterdunham|Walter Dunham]] | {{ls/domain|mstdn.social}} | Mastodon |} ==Footnotes== <references> <ref name=smuglo>{{ls/domain|gs.smuglo.li}} was blocked by the previous administration of toot.cat; I'm leaving that in place but not yet adding pl.smuglo.li. '''Update 2018-10-07''': They have now been blocked after a report from a known user.</ref> </references> 2488d5e4a72923b6e2ceca1388c64f7a34c9f27b 12 27 924 633 2023-12-31T17:36:09Z Woozle 1 some link updates wikitext text/x-wiki If you'd like to help support TootCat, there are several ways: <!-- ==Money== --> * '''TootCat''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** '''Buy my stuff!''' *** muzicks: [https://woozalia.bandcamp.com/ Bandcamp] **** also on Evil Platforms&trade;: [https://www.amazon.com/Rough-Draughts-Woozalia/dp/B07S1DG25W/ref=sr_1_1?keywords=Woozalia&qid=1558612080&s=gateway&sr=8-1 Amazon Music], [https://music.apple.com/us/album/rough-draughts/1464246974 iTunes/Apple Music], [https://open.spotify.com/artist/4ZvfiHyBo8Wf6zOg9kJNwV Spotify], [https://www.youtube.com/watch?v=YW3A2egQB5A&list=PLvxUl1l3W9mpMu-ftOsBcDqtNSNm4KTaD YouTube], [https://music.youtube.com/channel/UCTIoIWi4ZQD1fIi3iedSUzw YouTube Music] *** graphical merch: [https://woozalia.myspreadshop.com/ SpreadShop] (trans-related), [https://www.zazzle.com/store/woozalia Zazzle] (more political) (Please [https://toot.cat/@woozle let me know] if any of the merch/music links stop working.) I even accept checks (which still exist, somehow!): : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 <!-- ==Resources== We need to maintain a wish-list... * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) --> 5da3ff9c31be1129f5ba136004d88abbd1535ab0 963 924 2025-03-09T00:48:25Z Woozle 1 wikitext text/x-wiki If you'd like to help support TootCat, there are several ways: <!-- ==Money== --> * '''TootCat''': ** [https://liberapay.com/TootCat/ LiberaPay] * '''Woozle''' (hosting, primary admin): ** [https://liberapay.com/woozle/ LiberaPay] ** [https://www.patreon.com/woozalia Patreon] ** [https://paypal.me/woozalia PayPal] ** [https://account.venmo.com/u/Woozalia-Staddon Venmo] (@Woozalia-Staddon) - new for 2025! ** '''Buy my stuff!''' *** muzicks: [https://woozalia.bandcamp.com/ Bandcamp] **** also on Evil Platforms&trade;: [https://www.amazon.com/Rough-Draughts-Woozalia/dp/B07S1DG25W/ref=sr_1_1?keywords=Woozalia&qid=1558612080&s=gateway&sr=8-1 Amazon Music], [https://music.apple.com/us/album/rough-draughts/1464246974 iTunes/Apple Music], [https://open.spotify.com/artist/4ZvfiHyBo8Wf6zOg9kJNwV Spotify], [https://www.youtube.com/watch?v=YW3A2egQB5A&list=PLvxUl1l3W9mpMu-ftOsBcDqtNSNm4KTaD YouTube], [https://music.youtube.com/channel/UCTIoIWi4ZQD1fIi3iedSUzw YouTube Music] *** graphical merch: [https://woozalia.myspreadshop.com/ SpreadShop] (trans-related), [https://www.zazzle.com/store/woozalia Zazzle] (more political) (Please [https://toot.cat/@woozle let me know] if any of the merch/music links stop working.) I even accept checks (which still exist, somehow!): : Woozalia Staddon : 122 Pinecrest Rd. : Durham, NC 27705 <!-- ==Resources== We need to maintain a wish-list... * '''Charlotte''': ** [https://ko-fi.com/charlotte Ko-Fi] ** [https://www.patreon.com/CharlotteFields Patreon] ** <s>[https://liberapay.com/LottieVixen/ LiberaPay]</s> (not working as of 2021-03-21) --> a6e3186fa22863334576a88bc21a5a3770fe4f4d 0 89 925 683 2024-05-11T12:45:26Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-05-11''' No known problems. We are working on improving the upgrade and migration processes, and restoring our custom graphics.}} e0d027ae545d6914485451b8461b3043233ee8c8 926 925 2024-06-22T17:55:59Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-06-22''' We have a migration scheduled for 6-9 PM EST tonight! Updates will be posted here, at least if anything goes differently than planned.}} ec51c736a64ed07a6d9b1785a4c8b6b6eaee2c27 930 926 2024-06-22T22:13:32Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-06-22''' We had a migration scheduled for tonight, but that has been [https://toot.cat/@woozle/112662550006015493 postponed] for technical-optimization reasons.}} 80c2079f8cd7157f66b63767b0e2bc59507a5508 936 930 2024-06-29T23:09:16Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-06-29 (Sat)''' We are now starting the migration and upgrade! Watch this space for any news.}} 91e9b0e55120ef9f1706592ea503955002a339d1 937 936 2024-06-29T23:42:34Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-06-29 (Sat)''' We are now starting the migration and upgrade! Watch this space for any news. 19:42 EST: old server down, DNS propagation in progress, smol problem on other end..}} e3defe6722ddb90be37c8dbb21a1a687ca460825 938 937 2024-06-29T23:53:02Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-06-29 (Sat)''' Migration partly complete -- new server is still building stuff, but we have UI and some columns ^.^}} b5f521670a274c1e990e36d8a018fedf6a659aba 939 938 2024-06-30T00:07:20Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-06-29 (Sat)''' 20:06 EST Migration complete? Some things are being a bit odd, but hopefully they'll settle down...}} bfd8bfa93c10eaa210f21968cc699f8ad821dedf 946 939 2024-11-29T13:10:59Z Woozle 1 wikitext text/x-wiki {{hdr/notice/error|'''2024-11-29 (Fri)''' 08:09 EST Posting to TootCat is currently down; the problem may be a server outage at Hetzner. [[2024/11/29|We are investigating.]]}} 0014226db9fdb15555948b652df0300bd14347b6 957 946 2024-11-29T16:20:31Z Woozle 1 wikitext text/x-wiki {{hdr/notice/ok|'''2024-11-29 (Fri)''' 11:19 EST Everything ''seems'' to be working ok... ([[2024/11/29|details of last incident.]])}} a964e812fd71156cb453cae9ec6c3e38fdee50d3 966 957 2025-03-19T23:27:05Z Woozle 1 wikitext text/x-wiki {{hdr/notice/warn|'''2025-03-19 (Wed) 19:27 EDT''' Auto-updating of the main feed seems to be broken -- all day today, possibly 2-3 days. Trying to get leads on how to fix it.}} 7a451db1f536227869a66af712eae4ac399adfea 0 293 927 2024-06-22T21:43:19Z Woozle 1 Created page with "{{fmt/title|TootCat Technical Documentation|anything that's public-safe, anyway!}} ==Public Repositories== all on GitLab, for now: * [https://gitlab.com/tootcat/glitch Glitch]..." wikitext text/x-wiki {{fmt/title|TootCat Technical Documentation|anything that's public-safe, anyway!}} ==Public Repositories== all on GitLab, for now: * [https://gitlab.com/tootcat/glitch Glitch] (code): our lightly-tweaked Mastodon Glitch Edition * [https://gitlab.com/tootcat/boxes Boxes] (docs): some infrastructure, mainly to do with the 2024 migration * [https://gitlab.com/tootcat/nixos-config nixos-config] (code/docs): TC's NixOS configuration ** At least in theory, this is about to be obsolete. ** Many thanks to ash for getting it set up in a time of crisis. ==Domains== ==Servers== 4ea6ba212f6367c58930205c64fa5a851ea504fd 929 927 2024-06-22T22:10:51Z Woozle 1 wikitext text/x-wiki {{fmt/title|TootCat Technical Documentation|anything that's public-safe, anyway!}} ==Domains== Pretty much everything uses the <code>toot.cat</code> domain, currently registered with Gandi (we'd like to change that). Digital Ocean has been handling the DNS; that should probably change after the migration. ==Servers== Up until the June 2024 migration, we were using DigitalOcean. The plan is to migrate to Hetzner. ===DigitalOcean=== * 16 GB Memory / 320 GB Disk / NYC1 - Ubuntu 22.04 (LTS) x64 ($96/mo.) ==Public Repositories== all on GitLab, for now: * [https://gitlab.com/tootcat/glitch Glitch] (code): our lightly-tweaked Mastodon Glitch Edition * [https://gitlab.com/tootcat/boxes Boxes] (docs): some infrastructure, mainly to do with the 2024 migration ** @Meatballhat has been an absolute tank-demon (insert your own improved metaphor here) working on this. * [https://gitlab.com/tootcat/nixos-config nixos-config] (code/docs): TC's NixOS configuration ** At least in theory, this is about to be obsolete. ** Many thanks to ash for getting it set up in a time of crisis. d949882f81ed563baa4a38b6d9ab75e13a19de43 931 929 2024-06-22T22:42:19Z Woozle 1 wikitext text/x-wiki {{fmt/title|TootCat Technical Documentation|anything that's public-safe, anyway!}} ==Domains== Pretty much everything uses the <code>toot.cat</code> domain, currently registered with Gandi (we'd like to change that). Digital Ocean has been handling the DNS; that should probably change after the migration. {| class="wikitable sortable" ! Type || domain || value || TTL |- | A | staging.toot.cat | 5.161.31.3 | 60 |- | A | maintenance.toot.cat | 5.161.100.154 | 1800 |- | CNAME | grafana.toot.cat | lb.toot.cat. | 60 |- | A | lb.toot.cat | 5.161.31.3 | 1800 |- | CNAME | wiki.toot.cat | mew.toot.cat. | 43200 |- | A | grafana.staging.toot.cat | 143.198.26.211 | 60 |- | AAAA | grafana.ops.toot.catCopy directs to | 2604:a880:400:d0::2354:2001Copy | 3600 Copy More |- | A | grafana.ops.toot.cat | 143.244.160.92 | 3600 |- | AAAA | toot.cat | 2604:a880:400:d0::2354:2001 | 3600 |- | MX | toot.cat | toot.cat. | 14400 |- | TXT | toot_cat._domainkey.toot.cat | v=DKIM1; h=sha256; k=rsa;p=''[long base64 string]'' | 1800 |- | TXT | _dmarc.toot.cat | v=DMARC1; p=reject; rua=mailto:tootmaster2021@wooz.devCopy | 1800 |- | TXT | toot.cat | v=spf1 mx ip4:143.244.160.92 ip6:2604:a880:400:d0::2354:2001 -allCopy | 1800 |- | AAAA | hub.toot.cat | 2604:a880:400:d0::1a63:2001 | 3600 |- | A | hub.toot.cat | 68.183.140.54 | 3600 |- | AAAA | mew.toot.cat | 2604:a880:800:a1::126e:6001 | 3600 |- | A | mew.toot.cat | 165.227.176.23 | 3600 |- | A | toot.cat | 143.244.160.92 | 60 |} ==Servers== Up until the June 2024 migration, we were using DigitalOcean. The plan is to migrate to Hetzner. ===DigitalOcean=== * 16 GB Memory / 320 GB Disk / NYC1 - Ubuntu 22.04 (LTS) x64 ($96/mo.) ==Public Repositories== all on GitLab, for now: * [https://gitlab.com/tootcat/glitch Glitch] (code): our lightly-tweaked Mastodon Glitch Edition * [https://gitlab.com/tootcat/boxes Boxes] (docs): some infrastructure, mainly to do with the 2024 migration ** @Meatballhat has been an absolute tank-demon (insert your own improved metaphor here) working on this. * [https://gitlab.com/tootcat/nixos-config nixos-config] (code/docs): TC's NixOS configuration ** At least in theory, this is about to be obsolete. ** Many thanks to ash for getting it set up in a time of crisis. 9a879ac3cb81b55a9536f6b869b183fe20fe0f73 933 931 2024-06-22T22:47:27Z Woozle 1 wikitext text/x-wiki {{fmt/title|TootCat Technical Documentation|anything that's public-safe, anyway!}} ==Pages== * [[/domain]] ==Servers== Up until the June 2024 migration, we were using DigitalOcean. The plan is to migrate to Hetzner. ===DigitalOcean=== * 16 GB Memory / 320 GB Disk / NYC1 - Ubuntu 22.04 (LTS) x64 ($96/mo.) ==Public Repositories== all on GitLab, for now: * [https://gitlab.com/tootcat/glitch Glitch] (code): our lightly-tweaked Mastodon Glitch Edition * [https://gitlab.com/tootcat/boxes Boxes] (docs): some infrastructure, mainly to do with the 2024 migration ** @Meatballhat has been an absolute tank-demon (insert your own improved metaphor here) working on this. * [https://gitlab.com/tootcat/nixos-config nixos-config] (code/docs): TC's NixOS configuration ** At least in theory, this is about to be obsolete. ** Many thanks to ash for getting it set up in a time of crisis. 8a31357c42d85f0e2d2aa5ac505a325dd55de46e 0 1 928 766 2024-06-22T21:43:46Z Woozle 1 wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''MeW''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about * '''[[TootCat]]''': ** [[Toot.cat/CoC|Code of Conduct]] ** [[Toot.cat/CoJ|Code of Justice]] ** [[Help:Contribute]]: how to help keep us running ** [[Tech]]nical stuff, for those who celebrate ** [[.cat]]: about the TLD * '''Directories''': ** {{l/cat|Instance}}s: *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe * '''miscellaneous''': ** [[Quote toot]]: a much-requested but also much-loathed feature ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> c8bcb5e4ba21f66a1ef47c63824a185803beda49 962 928 2025-02-10T01:53:56Z Woozle 1 /* A Brief Directory */ wikitext text/x-wiki __NOTOC__ {{i/val|status|page=toot.cat}} <center> =Welcome to '''Me'''{{grey|''dia''}}'''W'''{{grey|''iki''}}!= </center> Most recent day-journal entry (probably): [[2022/11/18]] ==Meta== '''MeW''' is a community wiki<ref name=other /> for the [[Mastoverse]], with a focus on helping complicated people to be kind to each other. It's also the official wiki for '''[[toot.cat]]''', and we have started a '''[[cat|directory of cat-related things on the fediverse]]'''. We also offer space for Catalonian/Catalan interests, in order to help satisfy the [[.cat]] TLD requirements. ==A Brief Directory== * [[Mew:About]]: what this wiki is about * '''[[TootCat]]''': ** [[Help:Main]]: user help, including [[Help:TootCat/HTML/formatting/Markdown|Markdown]], [[Help:TootCat/HTML/formatting|HTML]], and [[Help:TootCat/HTML/enabling|how to enable them]]. ** [[Help:Contribute]]: how to help keep us running (aka the Tip Jar) ** [[Toot.cat/CoC|Code of Conduct]] ** [[Toot.cat/CoJ|Code of Justice]] ** [[Tech]]nical stuff, for those who celebrate ** [[.cat]]: about the TLD * '''Directories''': ** {{l/cat|Instance}}s: *** [[cat]]: cat-related things on the fediverse *** [[witches]]: witchy instances * [[woozle]]: ye olde sysoppe * '''miscellaneous''': ** [[Quote toot]]: a much-requested but also much-loathed feature ==Footnote== <references> <ref name=other>There is at least [https://en.mstdn.wiki/Main_Page one other] Mastodon wiki.</ref> </references> cca67db2afaa28539a084efb9c26890b22a18404 0 294 932 2024-06-22T22:46:24Z Woozle 1 Created page with "Pretty much everything uses the <code>toot.cat</code> TLD, currently registered with Gandi (we'd like to change that). Digital Ocean has been handling the DNS; that should pro..." wikitext text/x-wiki Pretty much everything uses the <code>toot.cat</code> TLD, currently registered with Gandi (we'd like to change that). Digital Ocean has been handling the DNS; that should probably change after the migration. The only other domain involved is the one listed for our contact email address -- using woozalia.com for now; eventually would like to make that an address @toot.cat or (something like) @mail.toot.cat. {| class="wikitable sortable" ! Type || domain || value || TTL |- | A | staging.toot.cat | 5.161.31.3 | 60 |- | A | maintenance.toot.cat | 5.161.100.154 | 1800 |- | CNAME | grafana.toot.cat | lb.toot.cat. | 60 |- | A | lb.toot.cat | 5.161.31.3 | 1800 |- | CNAME | wiki.toot.cat | mew.toot.cat. | 43200 |- | A | grafana.staging.toot.cat | 143.198.26.211 | 60 |- | AAAA | grafana.ops.toot.catCopy directs to | 2604:a880:400:d0::2354:2001Copy | 3600 Copy More |- | A | grafana.ops.toot.cat | 143.244.160.92 | 3600 |- | AAAA | toot.cat | 2604:a880:400:d0::2354:2001 | 3600 |- | MX | toot.cat | toot.cat. | 14400 |- | TXT | toot_cat._domainkey.toot.cat | v=DKIM1; h=sha256; k=rsa;p=''[long base64 string]'' | 1800 |- | TXT | _dmarc.toot.cat | v=DMARC1; p=reject; rua=mailto:tootmaster2021@wooz.devCopy | 1800 |- | TXT | toot.cat | v=spf1 mx ip4:143.244.160.92 ip6:2604:a880:400:d0::2354:2001 -allCopy | 1800 |- | AAAA | hub.toot.cat | 2604:a880:400:d0::1a63:2001 | 3600 |- | A | hub.toot.cat | 68.183.140.54 | 3600 |- | AAAA | mew.toot.cat | 2604:a880:800:a1::126e:6001 | 3600 |- | A | mew.toot.cat | 165.227.176.23 | 3600 |- | A | toot.cat | 143.244.160.92 | 60 |} 0b56060601a1593c84ea390ff89e2804fec3e391 934 932 2024-06-22T22:51:49Z Woozle 1 wikitext text/x-wiki Pretty much everything uses the <code>toot.cat</code> TLD, currently registered with Gandi (we'd like to change that). Digital Ocean has been handling the DNS; that should probably change after the migration. The only other domain involved is the one listed for our contact email address ([https://toot.cat/admin/settings/branding admin panel]) -- using woozalia.com for now; eventually would like to make that an address @toot.cat or (something like) @mail.toot.cat. {| class="wikitable sortable" ! Type || domain || value || TTL |- | A | staging.toot.cat | 5.161.31.3 | 60 |- | A | maintenance.toot.cat | 5.161.100.154 | 1800 |- | CNAME | grafana.toot.cat | lb.toot.cat. | 60 |- | A | lb.toot.cat | 5.161.31.3 | 1800 |- | CNAME | wiki.toot.cat | mew.toot.cat. | 43200 |- | A | grafana.staging.toot.cat | 143.198.26.211 | 60 |- | AAAA | grafana.ops.toot.catCopy directs to | 2604:a880:400:d0::2354:2001Copy | 3600 Copy More |- | A | grafana.ops.toot.cat | 143.244.160.92 | 3600 |- | AAAA | toot.cat | 2604:a880:400:d0::2354:2001 | 3600 |- | MX | toot.cat | toot.cat. | 14400 |- | TXT | toot_cat._domainkey.toot.cat | v=DKIM1; h=sha256; k=rsa;p=''[long base64 string]'' | 1800 |- | TXT | _dmarc.toot.cat | v=DMARC1; p=reject; rua=mailto:tootmaster2021@wooz.devCopy | 1800 |- | TXT | toot.cat | v=spf1 mx ip4:143.244.160.92 ip6:2604:a880:400:d0::2354:2001 -allCopy | 1800 |- | AAAA | hub.toot.cat | 2604:a880:400:d0::1a63:2001 | 3600 |- | A | hub.toot.cat | 68.183.140.54 | 3600 |- | AAAA | mew.toot.cat | 2604:a880:800:a1::126e:6001 | 3600 |- | A | mew.toot.cat | 165.227.176.23 | 3600 |- | A | toot.cat | 143.244.160.92 | 60 |} 2b26fcf9c8119298d1097e6de1ae3029e8009e35 935 934 2024-06-22T22:53:25Z Woozle 1 wikitext text/x-wiki Pretty much everything uses the <code>toot.cat</code> TLD, currently registered with Gandi (we'd like to change that). Digital Ocean has been handling the DNS; that should probably change after the migration. The only other domain involved is the one listed for our contact email address ([https://toot.cat/admin/settings/branding admin panel]) -- using woozalia.com for now; eventually would like to make that an address @toot.cat or (something like) @mail.toot.cat. {| class="wikitable sortable" ! Type || domain || value || TTL |- | A | staging.toot.cat | 5.161.31.3 | 60 |- | A | maintenance.toot.cat | 5.161.100.154 | 1800 |- | CNAME | grafana.toot.cat | lb.toot.cat. | 60 |- | A | lb.toot.cat | 5.161.31.3 | 1800 |- | CNAME | wiki.toot.cat | mew.toot.cat. | 43200 |- | A | grafana.staging.toot.cat | 143.198.26.211 | 60 |- | AAAA | grafana.ops.toot.cat | 2604:a880:400:d0::2354:2001 | 3600 |- | A | grafana.ops.toot.cat | 143.244.160.92 | 3600 |- | AAAA | toot.cat | 2604:a880:400:d0::2354:2001 | 3600 |- | MX | toot.cat | toot.cat. | 14400 |- | TXT | toot_cat._domainkey.toot.cat | v=DKIM1; h=sha256; k=rsa;p=''[long base64 string]'' | 1800 |- | TXT | _dmarc.toot.cat | v=DMARC1; p=reject; rua=mailto:tootmaster2021@wooz.dev | 1800 |- | TXT | toot.cat | v=spf1 mx ip4:143.244.160.92 ip6:2604:a880:400:d0::2354:2001 -all | 1800 |- | AAAA | hub.toot.cat | 2604:a880:400:d0::1a63:2001 | 3600 |- | A | hub.toot.cat | 68.183.140.54 | 3600 |- | AAAA | mew.toot.cat | 2604:a880:800:a1::126e:6001 | 3600 |- | A | mew.toot.cat | 165.227.176.23 | 3600 |- | A | toot.cat | 143.244.160.92 | 60 |} f31f9a8ebed6d4bf2a299312c3c324f0295dd212 0 208 940 724 2024-07-28T23:46:20Z Woozle 1 wikitext text/x-wiki [[category:UX]] ==About== A [[quote toot]] (quotoot or QT) is a [[toot]] (fediverse post) in which another toot is quoted, with additional commentary by the QTer. Although this can be done manually in a number of ways (i.e. by simply replying or linking to the original post and then pasting part or all of its contents into the new toot, preferably with clear indications that they are quoting the referenced toot), most discussion of this concept centers around whether it would be desirable as a feature for fediverse client-interface software (mainly [[Mastodon]]). While there are definitely beneficial ways to use such a feature, many people have apparently been quite traumatized by its abusive uses on Twitter (where it was, of course, known as "quote tweet[ing]"). ==Abuse Cases== Many people have cited the use of this feature on Twitter for harassing and starting dogpiles. ==Need Cases== * to add commentary * to add hashtags * to add a CW (content warning) * to put the post in a local context (this need might be better addressed by other means, but for the record) ** '''2022-12-22''' [https://github.com/mastodon/mastodon/discussions/22657 Web interface: Please localize all links. Clicking a link sometimes goes to another instance. #22657] (issue ticket on Mastodon repo) ** '''2022-12-22''' [https://social.vivaldi.net/@Patricia/109557071541332333 social.vivaldi.net/@Patricia] {{fmt/quote|When people follow a link to a post they end up on the server of the poster, but that has a generic “Mastodon” header that says they have to log in. So they think that is “log into ✨Mastodon✨” like it would for most of their other services. And when that fails (because they’re not on that server) then they ✨create new accounts✨.}} Note that different users have different followerships with different preferences and filtering needs; a post which may have been absolutely fine in the original poster's context might really need a CW (for content many followers might want to skip or only view under some circumstances) or hashtags (for filtering, as well as the more obvious use of making the post more findable) in the context of the person resharing it. ==Refinement== Something I have not seen brought up is that sometimes you don't want to quote an ''entire'' post, but maybe just a sentence or one or two paragraphs. I would definitely prefer to see an interface which presented the OP as editable content, rather than one which just embeds the original -- though if editing is ''not'' needed, embedding the original would be a nice ''option'' to have (especially when the original author might edit the post to correct errors or add updates). -W. ==Discussion== ===neutral/discuss=== * '''2022-12-27''' [https://toot.cat/@thatdawnperson/109585785337817705 toot.cat/@thatdawnperson] {{fmt/quote|It is important that QT protect the original writer’s distribution/privacy settings. What does QT safely give you that reply-and-boost or sharing a link doesn’t? [...]}} To my mind, this suggests one ''benefit'' of QT-as-a-feature over manually constructing them: they could encourage best practices, such as making sure QTs were replies rather than new threads, or not QTing if the quoted user has disabled them on a given post (or as a default for their account). * '''2022-12-24''' [https://wandering.shop/@annaleen/109570125073158983 Annalee Newitz] suggests a design feature that would alleviate their concerns (Annalee is generally against QTs) * '''2022-12-23''' [https://wandering.shop/@Quinnae_Moon/109566758700954368 wandering.shop/@Quinnae_Moon] {{fmt/quote|It appears, at least in my little archipelago of Mastodons, that there's a Great Quote-Tweet debate happening.}} thread with discussion * '''2022-12-18''' [https://toot.cat/@woozle/109537548294420159 toot.cat/@woozle] {{fmt/quote|So, let's talk about #quoteToots (known presumably as #quoteTweets on that other place).}} (discussion thread) ===negative/dislike=== * '''2022-12-24''' [https://wandering.shop/@cstross/109570385865573556 Annalee Newitz via Charlie Stross] (If image OCR is available in Linux, I don't know how to do it. -W.) * '''2022-12-24''' [https://chat.noelle.codes/@noelle/109569025317272042 chat.noelle.codes/@noelle]: comment from an experienced Twitter ''and'' Mastodon user, and instance admin (she's been on fedi since at least 2017, just not on that instance) * '''2022-12-19''' [https://indieweb.social/@whalecoiner/109547186015349835 indieweb.social/@whalecoiner] {{fmt/quote|I cannot describe to you the anxiety that comes from people demanding the fucking Quote feature for Mastodon.}} (thread, discussion) ===positive/want=== * '''2022-12-22''' [https://rage.love/@perigee/109558010645189617 rage.love/@perigee] {{fmt/quote|It seems like part of the discussion includes that (surprise) marginalized people use them for other purposes than the largely white developers seem to be able to conceive of.}} ... {{fmt/quote|if this pattern bears out, it'll be years or perhaps decades until there's a regime change and the feature request gets honored. Affably white folks who ignore requests sand discussion usually stick with it without critical engagement for their lifetime and never look back.}} A lot of vulnerable/marginalized people have also been traumatized by QTs on Twitter, though, it seems; that also needs to be taken into consideration. -W. * '''2022-12-21''' [https://fosstodon.org/@sehe/109554380574650275 fosstodon.org/@sehe] {{fmt/quote|about the ONLY thing that can NOT be conveniently shared on Mastodon is another Mastodon post. / Even embedding YT or Twitter links seems to work as expected. Why would toots be any different? It's effectively just Mastodon disadvantaging itself.}} * '''2022-11-16''' [https://hachyderm.io/@dalias/109355822005012040 hachyderm.io/@dalias] {{fmt/quote|OK, here it goes. Why quote-posting is a critical positive feature we need to get on this platform. [...]}} Enumerated thread. ==Notes== * At least one mobile client [https://floss.social/@megalodon/109554553454455272 now supports QTs]. ([https://toot.io/@rageagainstleaves/109558178041691593 screenshots]) 1cc8e46d45bf5ec00506be11a9c1ac1460865851 10 9 941 12 2024-09-23T15:44:48Z Woozle 1 wikitext text/x-wiki [https://{{{1|{{PAGENAME}}}}} {{{1|{{PAGENAME}}}}}] 3db7671d53f007a01cf37b7ef9752893e1daec08 0 295 942 2024-09-23T19:56:11Z Woozle 1 Created page with "[[category:instance]] [[category:Mastodon]] '''site''': {{ls/domain}} ==About== [[Strangeobject.space]] is a Mastodon instance which announced on 2024-09-23<ref name=sobj1 />..." wikitext text/x-wiki [[category:instance]] [[category:Mastodon]] '''site''': {{ls/domain}} ==About== [[Strangeobject.space]] is a Mastodon instance which announced on 2024-09-23<ref name=sobj1 /> that they will be ceasing operations "at the end of 2024" due to operator burnout. ==Footnote== <references> <ref name=sobj1> '''2024-09-23''' [https://blog.strangeobject.space/posts/2024-09-23-shutting-down.html Shutting Down] ([https://web.archive.org/web/20240923122229/https://blog.strangeobject.space/posts/2024-09-23-shutting-down.html archive.org]) </ref> </references> d2e28bbf5bc027cf4eebd8b701d891f034abe4ef 0 259 943 822 2024-09-23T21:12:41Z Woozle 1 /* Timeline (newest to oldest) */ wikitext text/x-wiki ===History=== TootCat was founded in 2017 by @polymerwitch and administered by @cyrinsong and @wavebeem, with moderation help from @ashkitten. In May, they created their own [https://github.com/TootCat/mastodon/ fork] of Mastodon 1.4.1, mainly to improve the layout somewhat and create a special English variant called "Catspeak" (code: en-TC) which replaced "boost" (reblog), "favorite", and "mention" with "bap", "boop", and "meow at". The team soon found itself overwhelmed with IRL responsibilities, however, and site maintenance declined. This started to become a problem when Mastodon 2.0 was released and Toot.Cat (which was still running 1.x) could no longer DM (direct message) most other instances; it finally became critical on approximately December 30, 2017, when the SSL certificate failed to auto-renew and the site became unreachable for most users. I ([[woozle]]) then offered to help with admin duties, to which @polymerwitch responded enthusiastically that she'd be happy to just have someone take over hosting and administration completely. The transfer took place in early January, 2018. I requested the aid of {{l/mastodon|cobaltvelvet|octodon.social}} in doing the upgrade to the then-current Mastodon version, as well as fixing the SSL issue, both of which she accomplished smoothly and quickly. ==Timeline (newest to oldest)== * 2024: Dan (@Meatballhat) [https://gitlab.com/tootcat/boxes converted it] to use Deployer and other associated tools, since neither of us were really able to understand how the Nix setup worked, and basically migrated it from DigitalOcean to Hetzner more or less singlehandedly<ref name=note1 /> * 2022: ** ash converted the server to NixOS, and created a failsafe deployment script. ** Viv has been massively helpful getting things upgraded. ** Dan has automated some processes and also handles upgrades. ** Ruby and Stephanie joined the mod team, helping to deal with the first massive Twitterfail influx (among other things). * 2020: Xenon Fiber joined the op team in 2020, replacing others who needed a break. * {{l/same|2018}}-03-30: Recognizing the need for some more easily-referenced online presence, I ([[@Woozle]]) set up this companion wiki (mew.toot.cat, what you're reading now). * {{l/same|2017}}-12-31: Ownership is handed over to @Woozle. Somewhere I have a link to an archive of the first Toot on TootCat... ==Footnote== <references> <ref name=note1>It's possible he used both hands on occasion, mostly for typing.</ref> </references> 6ee31bb11de940e56e302cb8811175e19b49b730 0 296 944 2024-10-29T23:56:31Z Woozle 1 Created page with "[[category:instance]] ==About== As of this writing (2024-10-29), [[botsin.space]] is a specialized Mastodon instance that is in the process of shutting down. The reasons for t..." wikitext text/x-wiki [[category:instance]] ==About== As of this writing (2024-10-29), [[botsin.space]] is a specialized Mastodon instance that is in the process of shutting down. The reasons for this decision, and a timetable for the shutdown, are detailed in a [https://muffinlabs.com/posts/2024/10/29/10-29-rip-botsin-space/ blog entry posted today], summarizable as "gradually escalating technical and financial [over]load". ==Links== * '''2024-10-29''' [https://muffinlabs.com/posts/2024/10/29/10-29-rip-botsin-space/ RIP botsin.space] ([https://archive.ph/6Krrp archive.ph]) c94d67af13b25bf7402d19a6a138611be4ef5ab5 945 944 2024-10-29T23:58:46Z Woozle 1 wikitext text/x-wiki [[category:instance]] ==About== As of this writing (2024-10-29), [[botsin.space]] is a specialized Mastodon instance that is in the process of shutting down. The reasons for this decision, and a timetable for the shutdown, are detailed in a [https://muffinlabs.com/posts/2024/10/29/10-29-rip-botsin-space/ blog entry posted today] and seem to boil down to gradually escalating technical and financial [over]load (a common problem among small-to-medium instances). ==Links== * '''2024-10-29''' [https://muffinlabs.com/posts/2024/10/29/10-29-rip-botsin-space/ RIP botsin.space] ([https://archive.ph/6Krrp archive.ph]) ca90d8f9113d489c9e9184a63cfcec0b9d8b932a 0 297 947 2024-11-29T13:14:20Z Woozle 1 Created page with "==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower rig..." wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. 0bd2f49d4a0aaefcf082a4d87e7d7bed214e5be0 948 947 2024-11-29T13:52:06Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. 5ac35a349d862d4d2dd6dd095bc7b428dff5385b 949 948 2024-11-29T14:32:02Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". e1e0a7a183140ce669d762ca1a3dd2780f42fe57 950 949 2024-11-29T14:35:02Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. 29bc0d9f7b452b1b395fc92b89f989dd2ea843be 951 950 2024-11-29T14:41:32Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''09:38 EST''' New posts from outside are also not coming in -- which would be consistent with a blockage between the back-end server and the rest of the internet. So we can see the server's current state, but it isn't communicating with the rest of fedi. I can access most of the cpanel, including moderation, but for some reason the [https://toot.cat/admin/dashboard admin panel] also returns an error; I'm not sure how that fits with my theory. * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. 59f11274f890fffcd49ea48978177f61516001cc 952 951 2024-11-29T14:42:45Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''09:38 EST''' New posts from outside are also not coming in (last new message was last night at 19:48 EST) -- which would be consistent with a blockage between the back-end server and the rest of the internet. So we can see the server's current state, but it isn't communicating with the rest of fedi. I can access most of the cpanel, including moderation, but for some reason the [https://toot.cat/admin/dashboard admin panel] also returns an error; I'm not sure how that fits with my theory. * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. 5bb940ad1e80ae69e391ee2ce0dd00b0fadf6cd1 953 952 2024-11-29T14:54:19Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''09:38 EST''' New posts from outside are also not coming in (last new message was last night at 19:48 EST) -- which would be consistent with a blockage between the back-end server and the rest of the internet. So we can see the server's current state, but it isn't communicating with the rest of fedi. I can access most of the cpanel, including moderation, but for some reason the [https://toot.cat/admin/dashboard admin panel] also returns an error; I'm not sure how that fits with my theory. * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. ** '''Note''': I figured this out before they disabled the cloud consoles. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. fabd057b651706ddb8bf58af9fa357df0fcdebc9 954 953 2024-11-29T14:56:57Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''09:55 EST''' I've confirmed that the cloud consoles are no longer accessible (disabled "to help us recover"), so this is definitely their issue. ** ...at least for now; if things don't start working again once they're done, then we'll have to resume investigating. * '''09:38 EST''' New posts from outside are also not coming in (last new message was last night at 19:48 EST) -- which would be consistent with a blockage between the back-end server and the rest of the internet. So we can see the server's current state, but it isn't communicating with the rest of fedi. I can access most of the cpanel, including moderation, but for some reason the [https://toot.cat/admin/dashboard admin panel] also returns an error; I'm not sure how that fits with my theory. * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. ** '''Note''': I figured this out before they disabled the cloud consoles. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. a8085ebb2f98c7903919429d3fb98dcae391e565 955 954 2024-11-29T15:27:10Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''09:55 EST''' I've confirmed that the cloud consoles are no longer accessible (disabled "to help us recover"), so this is definitely their issue. ** ...at least for now; if things don't start working again once they're done, then we'll have to resume investigating. * '''09:38 EST''' New posts from outside are also not coming in (last new message was last night at 19:48 EST) -- which would be consistent with a blockage between the back-end server and the rest of the internet. So we can see the server's current state, but it isn't communicating with the rest of fedi. I can access most of the cpanel, including moderation, but for some reason the [https://toot.cat/admin/dashboard admin panel] also returns an error; I'm not sure how that fits with my theory. * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. ** '''Note''': I figured this out before they disabled the cloud consoles. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 15:09 UTC+0''' The recovery is in progress. The systems are recovering slowly right now. *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. 8c21bb9e4be09cb93bb6f9ee7ffd4105872e2aef 956 955 2024-11-29T15:44:14Z Woozle 1 wikitext text/x-wiki ==Problem== Nobody can post or follow on TootCat, though the page seems to reload and remote updates are coming in. When trying to post, a "500" error appears in the lower right corner. ==Diagnosis== * '''10:27 EST''' ...and yet! It turns out that, by a curious coincidence, the root volume somehow got all filled up. (This is ''not'' where we keep the database or media files.) Once Dan removed a bunch of old, unneeded snapshot files, everything started working again (although Hetz had also reported that things were recovering on their end as well; hard to say if this would have worked before that point). ** Dan is tweaking the garbage-collection routines to catch this sort of thing in the future. * '''09:55 EST''' I've confirmed that the cloud consoles are no longer accessible (disabled "to help us recover"), so this is definitely their issue. ** ...at least for now; if things don't start working again once they're done, then we'll have to resume investigating. * '''09:38 EST''' New posts from outside are also not coming in (last new message was last night at 19:48 EST) -- which would be consistent with a blockage between the back-end server and the rest of the internet. So we can see the server's current state, but it isn't communicating with the rest of fedi. I can access most of the cpanel, including moderation, but for some reason the [https://toot.cat/admin/dashboard admin panel] also returns an error; I'm not sure how that fits with my theory. * '''08:50 EST''' Tentatively, the web servers and the database are fine -- but I need to discuss this with our web engineer (Dan) to confirm my understanding and work out a fix. I don't want to go making things worse with a poorly-conceived kluge that doesn't actually work. It looks like the load-balancer/firewall is the only thing affected, but I don't have a firm enough grasp of our architecture to be sure that this is the case or to be sure of how to temporarily work around it. ** '''Note''': I figured this out before they disabled the cloud consoles. * '''08:14 EST''' The problem may be a [https://status.hetzner.com/incident/c7a683c0-8216-45ef-87dc-1c8574ba714d service outage at Hetzner]. We're checking possibilities. ** This was originally "API failure (datacenters & locations)" but later changed to "Failures on API and Console". ** Updates from Hetzner: *** '''2024-11-29 15:09 UTC+0''' The recovery is in progress. The systems are recovering slowly right now. *** '''2024-11-29 14:08 UTC+0''' It is currently not possible to access the Cloud Console. This is intended to help us recover. *** '''2024-11-29 12:41 UTC+0''' Currently it is not possible to create or modify resources in the Hetzner Cloud. Already running resources are not affected. **** ...except it looks like our firewall/load-balancer is out of commission. -W. 37133d48018c2c4890f14bbe4bf87cd359cd3a77 0 48 958 846 2024-11-29T16:21:36Z Woozle 1 wikitext text/x-wiki [[category:Mastodon]] [[category:instance]] [[category:active]] {{i/val|status|page=toot.cat}} ==About== '''Toot.Cat''' has been online since [https://web.archive.org/web/20190607141308/https://toot.cat/@polymerwitch/1 2017-03-05]. * '''[[Help:TootCat|TootCat Help]]''' and FAQ * '''{{l/sub|history}}''': a brief and occasionally-updated history of our instance * '''{{l/sub|CoC}}: Code of Conduct * [[/blocks/domain|domain blocks]]: some details * [[/blocks/user|user blocks]] * [[/CoJ]]: Code of Justice * technical: [[/DNS]] ==Links== * '''official''': ** {{ls/domain|toot.cat}}: Mastodon entry page * '''news''': ** '''2017-06-21''' [http://opensourcebridge.org/sessions/2082 Federating With The Trouble - Running Decentralized Communities] ([https://web.archive.org/web/20190430191043/http://opensourcebridge.org/sessions/2082 archive.org]) "As moderators and admins of a mastodon/gnu social instance called Toot.Cat we were quickly propelled into navigating the strange new world of decentralized community stewardship." at [http://opensourcebridge.org/ Open Source Bridge] (in Portland, OR), [http://opensourcebridge.org/y2017/ 2017 edition] (#osb17) *** [https://toot.cat/@jdp23/981329 Live from #osb17 - Federating With the Trouble, presented by @cyrinsong @wavebeem and @polymerwitch!] ==Archives== * [[/2020]] * [[/2018]] * [[/2017]] 91a9d0a78f3898f4b5e15d380edcba561a624e0e 0 276 959 885 2024-12-04T15:06:32Z Woozle 1 /* Too Much Damn Power */ wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== [[File:Shuttering google reader.334841466545c250.jpeg|thumb|Google EEEd RSS feeds]] The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already '''{{l/sub|issues}}''' with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem ''for Mastodon'' (even being open-source and full-federated as it is) that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body; having the whole thing centrally owned and controlled is that same problem but larger by orders of magnitude. '''Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person.''' Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? (more: [[EEE]]) Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. (The same conditions should probably also apply to [[BlueSky]]; I'll eventually do a page about that when I have more information. -W.) ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> d5c9fa9a84c16521ecde596c2387471f95671691 960 959 2024-12-04T23:57:59Z Woozle 1 wikitext text/x-wiki [[Meta Threads]] (MT) refers to the ActivityPub app {{l/wp|Threads (app)|Threads}} released by {{l/wp|Meta Platforms}}, Inc. (formerly Facebook, Inc.) in July 2023. I had already decided, as of May or June, not to federate with MT<ref name=preblock /> for several reasons. We are, however, not taking any action against other instances who do choose to federate; this is a complex issue with room for legitimate disagreement, and I think it's important to encourage conversation in the independent fediverse around these topics. I have, in fact, signed the [https://fedipact.online anti-Meta fedipact]. ==Why are we blocking them?== Overall, it's a bit like the {{l/wikt|Nazi bar}} analogy<ref name=nazibar /> ===Roadblocking Corporate Takeover=== [[File:Shuttering google reader.334841466545c250.jpeg|thumb|Google EEEd RSS feeds]] The largest of these reasons was a desire to put every obstacle in the path of corporate dominance and control of the fediverse ("fedi") and/or the open [[ActivityPub]] standard. Corporate dominance and control over open standards and platform-genres has historically been carried out in the following ways (that I know of): * {{l/wp|Embrace, extend, and extinguish}} (EEE): enthusiastically support the protocol at first; then, offer your own supplementary standards which expand the capabilities of that protocol and, although technically "open", are difficult/expensive to implement; then get the majority of users captured by your implementations which depend on these new standards that you control, leaving the original standard meaningless. * To drain the lifeblood from independent hosts and development of the genuinely-open standard and implementations thereof. ===Too Much Damn Power=== It should also be noted that even if Threads turns out to be a completely benevolent entity (there are already '''{{l/sub|issues}}''' with it, so this seems unlikely), the simple fact of a platform being under ''effective'' central control is its own problem. It's already a problem ''for Mastodon'' (even being open-source and full-federated as it is) that the overwhelming bulk of contributed development money goes directly to Gargron rather than to a more accountable body; having the whole thing centrally owned and controlled is that same problem but larger by orders of magnitude. '''Development for any large software project should be funded by donations to an independent body, not by funds sent directly to a single person.''' Likewise, the problem of [[mastodon.social]] existing as the "flagship instance" and the default place for most signups existed long before MT. (Many newer users don't even realize that mastodon.social is not the same thing as Mastodon.) I could make an "elephant in the room" joke, but more accurately I'd compare it to inviting a supertanker into a small lake: there's not going to be a lot of water left for anyone else. Remember how Google+ drained the lifeblood from Diaspora, attracted a thriving and vibrant community that I enjoyed greatly, and then was quietly killed as a "failure" by arbitrary fiat of a single executive? (more: [[EEE]]) Yes, fedi ''can'' survive MT coming and going, but ''only if'' we resist the temptation to adopt any "innovations" they may bring to the table without first verifying that they do not create a suppressive effect on independent instances and development... and right now I have no confidence that Gargron even sees this as an issue. We need to be moving the other direction. ==Terms under which I'd reconsider== * Meta must fund a self-governed cooperative to manage development of the ActivityPub standard and implementation of it. ** Funding should be sufficient for, say, five years of five full-time developers. Let's say 100k/year for each developer, x5 devs x5 years = $2.5M. This would be a trivial amount to them, I should think, given how much they must have invested in Threads. ** The cooperative itself could decide how to actually spend this, but that would be enough to really focus on keeping the standard from being co-opted. ** Funding should be maintained at that level indefinitely, i.e. there should ''always'' be $2.5M in the coffers at the beginning of the fiscal year, so that Meta can't meaningfully exercise financial pressure by threatening to pull out if things don't go the way they want. * Meta must agree to full transparency over the data they collect and retain from each instance. * The Threads app must be open-source. If we are going to be able to defend ourselves against possible abuses from the 5000000-ton gorilla that is Meta, they need to share enough of their power to make coexistence possible and help level the playing field ''just a little''. Only this way can they prove that their intentions are truly benevolent. (They won't, because they aren't. This is me being reasonable and offering them a choice.) It's not going to happen, but that's what is needed. (The same conditions should probably also apply to [[BlueSky]]; I'll eventually do a page about that when I have more information. -W.) ==Notes== Not sure which of these are actually Facebook accounts: * 2019-02-24: [https://twitter.activitypub.actor/facebook twitter.activitypub.actor/facebook] * 2021-08-13: [https://birdsite.slashdev.space/users/fb_engineering birdsite.slashdev.space/users/fb_engineering] * 2021-10-29: [https://birdsite.slashdev.space/users/facebookapp birdsite.slashdev.space/users/facebookapp] ==Footnote== <references> <ref name=preblock>We also pre-emptively blocked a set of domains believed to be owned by Meta.</ref> <ref name=nazibar> * '''2023-04-24''' [https://kcraybould.substack.com/p/substack-notes-and-the-nazi-bar-problem Substack Notes and the Nazi Bar Problem] * '''2022-04-09''' [https://www.boredpanda.com/bar-bartender-nazi-punk-iamragesparkle/ Bartender Savagely Kicks A Polite Nazi Customer Out Of His Bar And Explains Why It’s Important To Do So]</ref> </references> ea7f3f9e3f5b89fb43621745aa9d62bb9df4a961 12 255 961 876 2025-02-10T01:48:37Z Woozle 1 wikitext text/x-wiki {{fmt/title|formatting posts with Markdown}} Remember that anything that works with the [[../|HTML option]] will also work with the Markdown option! I've also posted these examples [https://toot.cat/@woozle/110673322263974593 on TootCat] so you can see how they look in practice. <syntaxhighlight lang=md> Character formatting: ===================== * **bold** * *italic* * ~~strike~~ * _underline_ * `[link text](URL)` e.g. [toot.cat](https://toot.cat) - URL must include protocol:// * ^superscript -- like: E=MC^2 * I don't know how to turn it off without a space. * You can even do supersuperscript: Normal^super^hyper makes "hyper" look like a superscript on "super" -- both higher and smaller Lists: ====== * bullet item one * bullet item two * sub-item for item 2 (2 spaces per indent) * bullet item three 1. numbered list item 1 2. numbered list item 2 Fixed-pitch: ============ `inline fixed-pitch text` ``` multiline fixed-pitch text: multiple lines of fixed-pitch font (for pasting code examples and such) ``` Syntax highlighting does not seem to be supported at present. (Tsk tsk.) Text blocks: ============ # Header 1 ## Header 2 ### Header 3 > quote-indented text Be sure to leave a blank line after the last bit of indented text, or the renderer may decide it should also be indented. (Nobody knows why.) </syntaxhighlight> There's also a weird syntactical glitch which is probably not supported and may not always work, but which allows you to link to a tag without joining it ''while staying in the "deck" UI'' (i.e. opens in the right panel rather than a new tab), and also lets you put a secret message in the URL display in the bottom panel of most browsers. A demonstration is [https://toot.cat/@woozle/113977005250320776 here]. ==Further Reading on Markdown== Note that TootCat only supports a small ''subset'' of Markdown. * [[wikipedia:Markdown|Wikipedia]] * [https://daringfireball.net/projects/markdown/ official site] * [https://www.markdownguide.org/ Markdown Guide] 85d3cfc744eb1b94f33edd5126d0161342404392 0 298 964 2025-03-18T12:27:43Z Woozle 1 Created page with "==About== [[Nicole the Fediverse Chick]] is the self-identification of multiple accounts on various instances which all have similar profile descriptions and images. She began..." wikitext text/x-wiki ==About== [[Nicole the Fediverse Chick]] is the self-identification of multiple accounts on various instances which all have similar profile descriptions and images. She began appearing on fedi no later than 2025-02-18, randomly spamming users on other instances with copypasta. Her profile and header images all appear to be stills from a video call. There is evidence that Nicole is a real person, and that her profile description is accurate &ndash; while the use of video-call material for her profile suggests that she is not the one making the profiles or using them, leading to the theory that the operator of these accounts is seeking to defame Nicole for reasons unknown (the "vengeful stalker" hypothesis being the most obvious possibility). ==Details== @nicole78@mstdn.ro, @nicole53@chinanews.social, @nicole6@toot.io, @beyorkisan617095@tty0.social &ndash; <blockquote> Hi, I’m Nicole! But you can call me the Fediverse Chick 😎 I’m a proud Polish girl from Toronto (29 y/o) 🇨🇦 I’m currently taking the pre-health sciences program at George Brown College hoping to get into the medical field someday! </blockquote> Same text but no emoji: @nicole71@rheinneckar.social, @nicole8@liker.social, @nicole93@talk.stayas.one (Many of these accounts have been suspended, possibly all of them.) ==Links== * [https://feddit.org/c/nicole Nicoled]: Feddit forum * '''2025-03-17''' ** [https://mkultra.monster/social-media/2025/03/17/youve-been-nicoled You've Been Nicoled: A Fediverse User With Too Much Time On Her Hands, Or A Vengeful Stalker?] ** [https://transmom.love/@elilla/114177585280264890 I heard that Nicole the Fediverse Chick (Polish girl from Toronto)'s Discord is kinda dead so...] (thread) d79fcb03c9c895def37fd04f2e2ff86bc19e3848 965 964 2025-03-18T20:56:12Z Woozle 1 wikitext text/x-wiki ==About== [[Nicole the Fediverse Chick]] is the self-identification of multiple accounts on various instances which all have similar profile descriptions and images. She began appearing on fedi no later than 2025-02-18, randomly spamming users on other instances with copypasta. Her profile and header images all appear to be stills from a video call. There is evidence that Nicole is a real person, and that her profile description is accurate &ndash; while the use of video-call material for her profile suggests that she is not the one making the profiles or using them, leading to the theory that the operator of these accounts is seeking to defame Nicole for reasons unknown (the "vengeful stalker" hypothesis being the most obvious possibility). ==Details== @nicole78@mstdn.ro, @nicole53@chinanews.social, nicole66@chinanews.social, @nicole6@toot.io, @beyorkisan617095@tty0.social &ndash; <blockquote> Hi, I’m Nicole! But you can call me the Fediverse Chick 😎 I’m a proud Polish girl from Toronto (29 y/o) 🇨🇦 I’m currently taking the pre-health sciences program at George Brown College hoping to get into the medical field someday! </blockquote> Same text but no emoji: @nicole71@rheinneckar.social, @nicole8@liker.social, @nicole93@talk.stayas.one (Many of these accounts have been suspended, possibly all of them.) Sample posting (@-mentioning a TootCat user) from nicole66@chinanews.social on 2025-03-18: <blockquote> Hi, I’m Nicole! But you can call me the Fediverse Chick :D I’m a proud Polish girl from Toronto (29 y/o) I’m currently taking the pre-health sciences program at George Brown College hoping to get into the medical field someday! My dad just lost his job and I have no money for tuition next semester. Please help me raise money so I can keep going to school! Donate anything you can to these bitcoin and litecoin addresses <3 BTC: bc1q3qkfrdrgvj53aam8vm8l9q6ecqrdpysx2fwtr4 LTC: ltc1q38v </blockquote> ==Links== * [https://feddit.org/c/nicole Nicoled]: Feddit forum * '''2025-03-17''' ** [https://mkultra.monster/social-media/2025/03/17/youve-been-nicoled You've Been Nicoled: A Fediverse User With Too Much Time On Her Hands, Or A Vengeful Stalker?] ** [https://transmom.love/@elilla/114177585280264890 I heard that Nicole the Fediverse Chick (Polish girl from Toronto)'s Discord is kinda dead so...] (thread) 02e6d618f4fb17e88275219e898a8d1d83e53660